[gentoo-embedded] linking against gdbm fails when emerging python

[gentoo-embedded] linking against gdbm fails when emerging python

[Natanael Copa]

I am trying to upgrade to python 2.3.5-r2 but I get this error:


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

I dont have gdbm in the useflags.

I tried to reemerge gdbm, same thing happens.

I tried to enable gdbm in the useflags but same thing happens.

So I tried to re-emerge the current python with emerge
=dev-lang/python-2.3.5 but the same thing happens.

So I suspect that my build environment is broken somwhere somehow.

Maybe I used to have gdbm in the useflags but it have been removed?

Anyone experienced the same thing?
Shouldn't there be a -L/usr/lib instead of -L/usr/local/lib?
Does anyone have a suggestion how to bypass?

-- Natanael Copa

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] linking against gdbm fails when emerging python

[Mike Frysinger]

On Thursday 22 September 2005 05:33 am, Natanael Copa wrote:
> So I suspect that my build environment is broken somwhere somehow.

i'm not 100% sure it's your fault without double checking the ldso behavior

> Shouldn't there be a -L/usr/lib instead of -L/usr/local/lib?

no, that's a 'feature' of the braindead python build system

> Does anyone have a suggestion how to bypass?

do you have USE=gdbm ?
-mike
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] linking against gdbm fails when emerging python

[Natanael Copa]

thanks for replying Mike. Always nice having you around :-)

Mike Frysinger wrote:

>On Thursday 22 September 2005 05:33 am, Natanael Copa wrote:
>  
>
>>So I suspect that my build environment is broken somwhere somehow.
>>    
>>
>
>i'm not 100% sure it's your fault without double checking the ldso behavior
>  
>
>>Does anyone have a suggestion how to bypass?
>>    
>>
>
>do you have USE=gdbm ?
>  
>

No.

# portageq envvar USE
x86 X509 bitmap-fonts cracklib hardened jpeg mad minimal ncurses pcmcia
pic png readline rrdtool snmp truetype truetype-fonts uclibc winbind
zlib userland_GNU kernel_linux elibc_uclibc

Or... actually I have...???

alpine-testing:/ # emerge --info | grep USE
USE="x86 X509 berkdb bitmap-fonts cdr cracklib curl gd gdbm hardened
jpeg mad minimal ncurses ogg pcmcia pic png readline rrdtool snmp sqlite
ssl truetype truetype-fonts uclibc vorbis winbind xml2 zlib userland_GNU
kernel_linux elibc_uclibc"

How come?

# emerge -pv python | grep gdbm
[ebuild     U ] dev-lang/python-2.3.5-r2 [2.3.5] -X +berkdb -bootstrap
-build -doc -gdbm -ipv6 +ncurses -nocxx +readline +ssl -tcltk -ucs2 0 kB


Do I have USE="gdbm" or not?

--
Natanael Copa

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] linking against gdbm fails when emerging python

[Mike Frysinger]

On Thursday 22 September 2005 09:43 am, Natanael Copa wrote:
> Mike Frysinger wrote:
> >On Thursday 22 September 2005 05:33 am, Natanael Copa wrote:
> >>Does anyone have a suggestion how to bypass?
> >
> >do you have USE=gdbm ?
>
> No.
>
> # portageq envvar USE
> x86 X509 bitmap-fonts cracklib hardened jpeg mad minimal ncurses pcmcia
> pic png readline rrdtool snmp truetype truetype-fonts uclibc winbind
> zlib userland_GNU kernel_linux elibc_uclibc
>
> Or... actually I have...???
>
> alpine-testing:/ # emerge --info | grep USE
> USE="x86 X509 berkdb bitmap-fonts cdr cracklib curl gd gdbm hardened
> jpeg mad minimal ncurses ogg pcmcia pic png readline rrdtool snmp sqlite
> ssl truetype truetype-fonts uclibc vorbis winbind xml2 zlib userland_GNU
> kernel_linux elibc_uclibc"
>
> How come?

use.defaults, see info in portage(5) about the file

if you do not explicitly have '-gdbm' in your USE and you have gdbm emerged, 
then 'gdbm' will be added to USE automagically for you

so put -gdbm into USE in /etc/make.conf

> # emerge -pv python | grep gdbm
> [ebuild     U ] dev-lang/python-2.3.5-r2 [2.3.5] -X +berkdb -bootstrap
> -build -doc -gdbm -ipv6 +ncurses -nocxx +readline +ssl -tcltk -ucs2 0 kB

this wrong output is a bug which should be filed at bugs.gentoo.org
-mike
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] linking against gdbm fails when emerging python

[Natanael Copa]

Mike Frysinger wrote:

>so put -gdbm into USE in /etc/make.conf
>  
>

I did that. but python fails with same error again.

>># emerge -pv python | grep gdbm
>>[ebuild     U ] dev-lang/python-2.3.5-r2 [2.3.5] -X +berkdb -bootstrap
>>-build -doc -gdbm -ipv6 +ncurses -nocxx +readline +ssl -tcltk -ucs2 0 kB
>>    
>>
>
>this wrong output is a bug which should be filed at bugs.gentoo.org
>  
>

I will, when the 'emerge -e world' is done and if the problem still is
there.

--
Natanael Copa
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] linking against gdbm fails when emerging python

[Natanael Copa]

Mike Frysinger wrote:

>># emerge -pv python | grep gdbm
>>[ebuild     U ] dev-lang/python-2.3.5-r2 [2.3.5] -X +berkdb -bootstrap
>>-build -doc -gdbm -ipv6 +ncurses -nocxx +readline +ssl -tcltk -ucs2 0 kB
>>    
>>
>
>this wrong output is a bug which should be filed at bugs.gentoo.org
>  
>

It wasn't wrong output. I had -gdbm in /etc/portage/package.use

-- 
Natanael Copa


-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] linking against gdbm fails when emerging python

[Mike Frysinger]

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 ...
-mike
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] linking against gdbm fails when emerging python

[Natanael Copa]

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 ...
>-mike
>  
>

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)

I worked around it by adding "dev-lang/python -berkdb" in
/etc/portage/package.use so its no stopper for me.

I can report a bug if you'd like.

--
Natanael Copa
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] linking against gdbm fails when emerging python

[Mike Frysinger]

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
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] linking against gdbm fails when emerging python

[Natanael Copa]

On tir, 2005-12-27 at 03:33 -0500, Mike Frysinger wrote:
> 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 ...

[ebuild   R   ] dev-lang/python-2.4.2  -X +berkdb* -bootstrap -build
-doc -gdbm -ipv6 +ncurses -nocxx +readline +ssl -tcltk -ucs2 0 kB


i386-gentoo-linux-uclibc-gcc -pthread -shared -fno-strict-aliasing
-DNDEBUG -march=i386 -Os -pipe -fomit-frame-pointer
build/temp.linux-i686-2.4/_bsddb.o -L/usr/lib -L/usr/local/lib
-R/usr/lib -ldb-4.2 -o build/lib.linux-i686-2.4/_bsddb.so
i386-gentoo-linux-uclibc-gcc: unrecognized option `-R/usr/lib'
building 'dbm' extension
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.4.2/work/Python-2.4.2/./Include
-I/var/tmp/portage/python-2.4.2/work/Python-2.4.2/Include
-I/var/tmp/portage/python-2.4.2/work/Python-2.4.2
-c /var/tmp/portage/python-2.4.2/work/Python-2.4.2/Modules/dbmmodule.c
-o build/temp.linux-i686-2.4/dbmmodule.o
i386-gentoo-linux-uclibc-gcc -pthread -shared -fno-strict-aliasing
-DNDEBUG -march=i386 -Os -pipe -fomit-frame-pointer
build/temp.linux-i686-2.4/dbmmodule.o -L/usr/local/lib -lgdbm -o
build/lib.linux-i686-2.4/dbm.so
./python: can't resolve symbol 'dbm_firstkey'
make: *** [sharedmods] Error 1

using uclibc-0.9.27-r1.

I have turned of berkdb in useflags, so you don't need to spend time on
this for me.

btw... any idea on when 0.9.28 will go stable?

Thanks!


-- 
Natanael Copa

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] linking against gdbm fails when emerging python

[Mike Frysinger]

On Tuesday 27 December 2005 04:33, Natanael Copa wrote:
> using uclibc-0.9.27-r1.

hmm, i'll see if i can find a 0.9.27-r1 system around ...

> btw... any idea on when 0.9.28 will go stable?

just before the 2006.0 release ... which is slated for first quarter 2006

ive already built stages for arm/i386/sh with 0.9.28 though, so it should be 
pretty good
-mike
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] linking against gdbm fails when emerging python

[Natanael Copa]

On tir, 2005-12-27 at 04:39 -0500, Mike Frysinger wrote:
> On Tuesday 27 December 2005 04:33, Natanael Copa wrote:
> > using uclibc-0.9.27-r1.
> 
> hmm, i'll see if i can find a 0.9.27-r1 system around ...

You can find my system here: http://jv.lmdata.org/alpine/hardened

There should be a buildbase (built from emerge -e system) and a bunch of
binary packages.

-- 
Natanael Copa

-- 
gentoo-embedded@gentoo.org mailing list