> Try binutils-2.16.91.0.3 and 2.16.91.0.4 if you can (they're not keyworded,
> so you'll have to employ an overlay or the files in /etc/portage to unmask
> them). I know that 2.16.91.0.3 acts funny on glibc (iirc), but I haven't
> tested 2.16.91.0.4 on anything.

The temacs binary built with either of them breaks in the same way as before.
I'm currently rebuilding glibc and GCC with binutils-2.16.91.0.4, since:
1) The system is built with binutils-2.16.90.0.3.
2) Emacs built with binutils-2.16.90.0.3 works (sort of).
3) Emacs doesn't build with any other binutils version.
Hypothesis: Emacs needs to be built with the same binutils as something else.
Check: Rebuild system with 2.16.91.0.4, rebuilding Emacs works.
Hypothesis: Emacs only builds with 2.16.90.0.3 (of those versions >= 2.16.1
available in Portage).
Check: Rebuild system with 2.16.91.0.4, rebuilding Emacs fails, downgrade to
binutils-2.16.90.0.3, rebuilding Emacs works.
Hmm. While I was writing that, the build of glibc with binutils-2.16.91.0.4
failed with:
{standard input}: Assembler messages:
{standard input}:765: Error: symbol `__divdi3' is already defined
{standard input}:830: Error: symbol `__moddi3' is already defined
{standard input}:905: Error: symbol `__udivdi3' is already defined
{standard input}:934: Error: symbol `__umoddi3' is already defined
make[2]: *** [/var/tmp/portage/glibc-2.3.5-r2/work/build-default-
mips-unknown-linux-gnu-linuxthreads/csu/divdi3.os] Error 1
New plan: Rebuild everything with binutils-2.16.1 instead of 2.16.91.0.4. That
should only take a week...
--
Karl-Johan "Creideiki" Karlsson