[gentoo-user] amd64-hardened breaks upon glibc emerge

[gentoo-user] amd64-hardened breaks upon glibc emerge

[Roman Zilka]

Hi everyone!

I've been trying to install hardened-amd64 non-multilib Gentoo on my new
box, but I keep hitting bug #122274 (comment #2) or something similar.
I fetch the latest stage3 and portage snapshot, chroot into this
environment, 'emerge --sync', 'emerge portage', 'emerge -C pam-shadow',
'emerge shadow pam openssh', 'emerge gcc glibc' which results in an
unusable system. Any consequent emerge I've tried crashes
upon the first gcc call with the same error:

/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find /usr/lib64/libc_nonshared.a

The original stage3's /usr/lib64 does contain this
library, but after the upgrade of glibc it shows up in /usr/lib. The
only solution I could make up was to move everything from /usr/lib
to /usr/lib64, symlink /usr/lib -> /usr/lib64 and then start emerging
things (including glibc). But this tweak seems just unclean
and potentially dangerous. Does anybody happen to have an idea as to how
get things running in a proper and clean way? Some relevant info about the
system attached at the end. Thanks in advance for any hint or
pointer. The aforementioned bug has been reopened for quite some
time without any visible progress (maybe things are supposed to be OK now).

Regards
-Roman

-----------------
Profile: /usr/portage/profiles/hardened/amd64
C(XX)FLAGS: "-O2 -pipe
-fomit-frame-pointer -march=athlon64 -mmmx -msse -msse2 -m3dnow"
# emerge -pv glibc | grep USE
[ebuild   R   ] sys-libs/glibc-2.3.6-r4  USE="hardened nls nptl -build
-erandom -glibc-compat20 -glibc-omitfp -nptlonly -profile" 0 kB
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] amd64-hardened breaks upon glibc emerge

[Richard Fish]

On 7/7/06, Roman Zilka <rzilka@gvid.cz> wrote:
> library, but after the upgrade of glibc it shows up in /usr/lib. The
> only solution I could make up was to move everything from /usr/lib
> to /usr/lib64, symlink /usr/lib -> /usr/lib64 and then start emerging

Actually seems like bug #133547, in which case it seems like you did
the right thing to fix.  This bug seems to be fixed in
baselayout-1.12.0 (see /usr/portage/sys-apps/baselayout/ChangeLog),
but unfortunately both 1.12.0-r1 and 1.12.1 are still ~amd64.  So what
you may need to do before updating gcc or glibc is:

echo "<=sys-apps/baselayout-1.12.99 ~amd64" >>/etc/portage/package.keywords
emerge -u baselayout

HTH,
-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] amd64-hardened breaks upon glibc emerge

[Roman Zilka]

> > library, but after the upgrade of glibc it shows up in /usr/lib. The
> > only solution I could make up was to move everything from /usr/lib
> > to /usr/lib64, symlink /usr/lib -> /usr/lib64 and then start emerging
> 
> Actually seems like bug #133547, in which case it seems like you did
> the right thing to fix.  This bug seems to be fixed in
> baselayout-1.12.0 (see /usr/portage/sys-apps/baselayout/ChangeLog),
> but unfortunately both 1.12.0-r1 and 1.12.1 are still ~amd64.  So what
> you may need to do before updating gcc or glibc is:
> 
> echo "<=sys-apps/baselayout-1.12.99 ~amd64" >>/etc/portage/package.keywords
> emerge -u baselayout

I followed this recipe - (a fresh --sync'd system) -> 'emerge portage' ->
'emerge baselayout' (1.12.1) -> 'emerge gcc glibc' - and I'm stuck again,
with the same problem. At any rate, thank you for your reply.

-Roman
-- 
gentoo-user@gentoo.org mailing list