glibc-2.3.5 emerge fail in post-inst borked system [SOLVED]

[gnomeza]

ARG.

I borked my system, and I need some suggestions:

I emerged sys-libs/glibc-2.3.5 (during a routine emerge -u world) and it failed during post-inst. Immediately afterwards almost everything I attempted to run (df, cp, ldconfig) segfaulted.
On reboot it got as far as freeing unused kernel memory (I guess this means that init fails).

I have both nptl and linuxthreads enabled for glibc.
I should've got a log of the exact error, but didn't - isn't that always what happens...

I tried the Gentoo 1.4 PPC LiveCD and chrooted my borked system but of course the 2.4.21 kernel version can't build nptl glibc.
I'm going to try reemerging glibc-2.3.5 without nptl and hopefully that will be good enough to be able to boot my system again.

So, any helpful tips?
Anyone else successfully or unsuccessfully emerged glibc-2.3.5?

------------
Powerbook5,4 G4 1.25GHz, 15"
kernel-2.6.11.4
_________________
http://markferry.net

[bkunlimited]

i saw several threads according to glibc-2.3.5. To make it short: which version of gcc did you use?

[gnomeza]

I was using gcc 3.4.3-20050110-r2, which is the most recent ~ppc GCC.

I solved the problem by emerging a linuxthreads (no nptl) glibc-2.3.5 with my 2.4.21-kernel ppc LiveCD - that allowed me to boot my system successfully - then setting USE=nptlonly and emerging glibc-2.3.5 again (which completed successfully).

So I'm leaving nptl and nptlonly in my USE flags from now on...
_________________
http://markferry.net