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