Just for fun, I tried to recompile binutils-2.13.90.0.18.ebuild after turning on the static keyword. The build dies eventually when it tries to pass the option "-all-static" to gcc: checking for gcc... (cached) gcc checking whether the C compiler (gcc -march=athlon-tbird -O3 -pipe -all-static) works... no configure: error: installation or configuration problem: C compiler cannot create executables. make: *** [configure-binutils] Error 1 !!! ERROR: sys-devel/binutils-2.13.90.0.18 failed. !!! Function src_compile, Line 84, Exitcode 2 !!! (no error message)
Yep, -all-static is not valid for gcc3. Static support in binutils dont work anyhow, so ill rip it when I get the time.
I tried binutils-2.13.90.0.16-r1 with the static use variable, and it compiles fine. I did not figure out what the configure scripts are doing differently with LDFLAGS, though. Derek
Prob do not use LDFLAGS in internal ./configure's as it does in .18. Anyhow, even though it does compile, you still do not get statically linked binaries ...
Martin, Is this a blocker for getting .8-r1 to stable?
one and a half year is enough. Either the problem became imminent or disappeared. Apparently it did not become imminent, otherwise the bug would have been treated with more attention. Sincerely, Alex