[gentoo-amd64] Re: glibc-2.12.1-r1 failure

[Duncan]

Paul Stear posted on Mon, 27 Sep 2010 13:33:22 +0100 as excerpted:

> Makefile:72: warning: overriding commands for target
> `/var/tmp/portage/sys-libs/glibc-2.12.1-r1/work/build-x86-x86_64-pc-
linux-gnu-nptl/login/pt_chown'
> ../Rules:120: warning: ignoring old commands for target
> `/var/tmp/portage/sys-libs/glibc-2.12.1-r1/work/build-x86-x86_64-pc-
linux-gnu-nptl/login/pt_chown'
> mkdir /var/tmp/portage/sys-libs/glibc-2.12.1-r1/image/sbin
> unexpected reloc type in static binary
> make[1]: *** [install-symbolic-link] Error 139
> make: *** [install] Error 2
> emake failed
>

> ~/ > emerge --info
> Portage 2.1.9.11 (default/linux/amd64/10.0/desktop, gcc-4.4.4,
> glibc-2.11.2-r0, 2.6.34-gentoo-r2 x86_64)

> ccache version 2.4 [enabled]

> ACCEPT_KEYWORDS="amd64 ~amd64"

> CFLAGS="-Os -march=k8 -mno-tls-direct-seg-refs -mmmx -msse3 -pipe
> -fomit-frame-pointer"

> FEATURES="assume-digests binpkg-logs ccache distlocks fixlafiles
> fixpackages metadata-transfer news parallel-fetch protect-owned sandbox
> sfperms strict unknown-features-warn unmerge-logs unmerge-orphans
> userfetch"

> MAKEOPTS="-j5 -s"

No specific help on your error, but...

One troubleshooting tip, when there are build issues, is to switch to
MAKEOPTS=-j1, forcing it to serialize so the error won't be mixed in with 
a bunch of extraneous "noise" from other make jobs.  The -s may or may not 
matter, but might as well eliminate it for the test as well, just in case.

IOW, I'm not sure if those warnings are related or not, and with multiple 
jobs, it's quite possible the error is actually some way above the bit 
that you posted.  -j1 solves that sort of problem as unlike with multiple 
make jobs, there's normally very little else after the error, with it.

Meanwhile, AFAIK entirely unrelated to your problem but I'm curious as I 
always like to see what other people have in their CFLAGS when I have a 
chance, why are you using -mno-tls-direct-seg-refs ?  I don't see anything 
in the gcc manpage info on that machine/arch-flag to suggest why I might 
wish to disable it, and it seems a rather odd arch-flag to simply throw in 
at random, so I'm wondering what the reasoning is.  I'm definitely NOT 
saying it's wrong.  Quite the contrary; with a bit more info, I might find 
it useful here... or not, but I don't know at this point.  So got a link 
or something I could read?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman