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

[Mike Frysinger <vapier@gentoo.org>]

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