Awhile back I submitted a bug on binutls that turned out to be a problem with hash-style on MPIs. I am still trying to figure out how to deal with it, although I guess it is officially "solved." My current problem is upgrading the kernel from 2.6.23.14-mipsgit-20080206 to 2.6.24.7-20080519. Just doing a make oldconfig, I get:

Which again is the hash problem. It's not really clear to me what the problem or solution has been. I have binutils-2.18-r3 and glibc-2.6.1 and my machine is otherwise up-to-date and I'm using the current 2008.0 profile. So what gives? Can anyone explain what is going on here?

PS The only thing I didn't update lately is I never *re-*built glibc when the CROSSCOMPILE_OPTS="-headers-only%" flag showed up, but I assume that doesn't make any difference. Also, I should mention I have continued to compile with LDFLAGS="-Wl,--hash-style=sysv" in /etc/make.conf.

Vapier tried one fix to the 77_all_generate-gnu-hash.patch file, but that didn't work on my end, so the bug has been re-opened for further review.

For now, the quick fix is to exclude 77_all_generate-gnu-hash.patch from the compile. Use 'ebuild' to unpack the ebuild, kill the patch, then finish using 'ebuild' to compile and merge it._________________"The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic

...and apply the 2 patches from bug #233229 while you're at it.
For some reason the new binutils-2.18-r3 are seriously broken without
them (a.k.a. happily segfaulting)

Yeah, I found that out. The plus was there actually was a fix for it.

Right now, if you build binutils-2.18-r3 and gcc-4.3.1-r1, then attempt to compile glibc-2.7 or even the 2.8_pre we have, you'll hose your system (unless you have a backup). I'm attempting to pin down the appropriate binutils patches to apply that might fix this (assuming binutils is the one that even needs fixing)._________________"The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic

...and apply the 2 patches from bug #233229 while you're at it.
For some reason the new binutils-2.18-r3 are seriously broken without
them (a.k.a. happily segfaulting)

Yeah, I found that out. The plus was there actually was a fix for it.

Right now, if you build binutils-2.18-r3 and gcc-4.3.1-r1, then attempt to compile glibc-2.7 or even the 2.8_pre we have, you'll hose your system (unless you have a backup). I'm attempting to pin down the appropriate binutils patches to apply that might fix this (assuming binutils is the one that even needs fixing).

What confuses me is that 2.18-r3 used to work without a hitch from the first time it hit portage.
I only noticed the breakage when I rebuilt it with a different host tuple on the target last week.
(mipsel-unknown-linux-gnu -> mipsel-softfloat-linux-gnu).