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

[Natanael Copa <mlists@tanael.org>]

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