On Monday 26 September 2005 03:32, Natanael Copa wrote: > Mike Frysinger wrote: > >On Thursday 22 September 2005 05:33 am, Natanael Copa wrote: > >>i386-gentoo-linux-uclibc-gcc -pthread -DNDEBUG -march=i386 -Os -pipe > >>-fomit-frame-pointer -fPIC -fno-strict-aliasing -DHAVE_GDBM_NDBM_H -I. > >>-I/var/tmp/portage/python-2.3.5-r2/work/Python-2.3.5/./Include > >>-I/var/tmp/portage/python-2.3.5-r2/work/Python-2.3.5/Include > >>-I/var/tmp/portage/python-2.3.5-r2/work/Python-2.3.5 -c > >>/var/tmp/portage/python-2.3.5-r2/work/Python-2.3.5/Modules/dbmmodule.c > >>-o build/temp.linux-i686-2.3/dbmmodule.o > >>i386-gentoo-linux-uclibc-gcc -pthread -shared > >>build/temp.linux-i686-2.3/dbmmodule.o -L/usr/local/lib -lgdbm -o > >>build/lib.linux-i686-2.3/dbm.so > >>./python: can't resolve symbol 'dbm_firstkey' > >>make: *** [sharedmods] Error 1 > > > >so you're still hitting this linker bug ? just wondering whether i should > >start poking at it or assume that it's been resolved one way or another > > ... > > Yes. It still fails whenever berkdb are in useflags. It looks like it > works with or without gdbm in useflags (as long berkdb is disabled)
just for python-2.3.x ? using uclibc-0.9.28 / python-2.4.x over here and it emerges fine with USE=berkdb ... -mike -- [email protected] mailing list
