Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 88734 - Emerging pam_console To An Alternate Root Fails Due To Path Issue For glib
Summary: Emerging pam_console To An Alternate Root Fails Due To Path Issue For glib
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: PAM Gentoo Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-11 08:33 UTC by Jayson Vantuyl
Modified: 2005-07-04 07:50 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jayson Vantuyl 2005-04-11 08:33:48 UTC
Emerging a system with `USE="-X -gtk -svga" ROOT=/tmp/firewall emerge iptables' failed with "gcc: /tmp/firewall//usr/lib/libglib.a not found".

Reproducible: Always
Steps to Reproduce:
1.mkdir /tmp/firewall
2.USE="-X -gtk -svga" ROOT=/tmp/firewall emerge iptables
3.

Actual Results:  
Failed with:

gcc: /tmp/firewall//usr/lib/glib.a not found

Expected Results:  
It should have emerged a basic system suitable for chrooted operation.

PAM is being built to satisfy baselayout.  PAM requires a static glib to link
into pam_console and pam_pwdb (according to comments in the ebuild).  Thisis
not present in the chroot and can't be built until baselayout is.  PAM does have
a proper dependency, but I'm not sure why glib isn't built first although I
suspect it may be a dependency on glibc in glib (which pam doesn't depend on).

I can work around this for now by emerging glib manually with:
USE="-X -svga -gtk" ROOT=/tmp/firewall emerge --nodeps '<dev-libs/glib-1.3'
Comment 1 Jayson Vantuyl 2005-04-11 09:26:11 UTC
Also had issue emerging PAM due to missing pwdb dependency.  Since this still prevents PAM from bootstrapping, I'm including it here (as that's my problem).
Comment 2 Martin Schlemmer (RETIRED) gentoo-dev 2005-07-04 07:50:07 UTC
It should have pulled in glib ... verify that that was installed to the chroot,
and reopen if still an issue after that.