On 03/03/12 23:44, Andrew Benton wrote: > On Sat, 03 Mar 2012 10:53:46 -0600 > Bruce Dubbs<[email protected]> wrote: > >> That was added 3 years ago and replaced a patch that did something >> similar. (Rev 7767) (python-2.6.1). It may not be needed any more. >> >> The sed still applies at line 1162, but looking at the code, line 1142 >> may mean it's not needed. > > So would it be Ok if I removed it? > > Andy
Without the sed, I get this error message at the end when running "make": Failed to build these modules: dbm This is how the "dbm" module is compiled: gcc -pthread -fPIC -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DHAVE_NDBM_H -I. -IInclude -I./Include -I/pkg/build/Python-2.7.2/Include -I/pkg/build/Python-2.7.2 -c /pkg/build/Python-2.7.2/Modules/dbmmodule.c -o build/temp.linux-i686-2.7/pkg/build/Python-2.7.2/Modules/dbmmodule.o gcc -pthread -shared build/temp.linux-i686-2.7/pkg/build/Python-2.7.2/Modules/dbmmodule.o -L. -lpython2.7 -o build/lib.linux-i686-2.7/dbm.so *** WARNING: renaming "dbm" since importing it failed: build/lib.linux-i686-2.7/dbm.so: undefined symbol: dbm_nextkey With the sed, "-lgdbm -lgdbm_compat" is added when linking the module, and I don't get the linker error or the error message at the end of the build. I have installed all packages in LFS except for udev and vim, and from BLFS I have installed pciutils, libusb, usbutils, gperf, attr, acl, libffi, PCRE, and Berkeley DB. Maybe I need to install some other package to make it work? -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
