Hi, just tried to install libstdc++-v3-3.3.3-r1. But it failed with this line: checking whether the C compiler ( /var/tmp/portage/libstdc++-v3-3.3.3-r1/work/build/gcc/xgcc -B/var/tmp/portage/libstdc++-v3-3.3.3-r1/work/build/gcc/ -B/usr/powerpc64-unknown-linux-gnu/bin/ -B/usr/powerpc64-unknown-linux-gnu/lib/ -isystem /usr/powerpc64-unknown-linux-gnu/include -O2 -mcpu=G5 -pipe -O2 ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. make: *** [configure-target-libiberty] Error 1 !!! Error: sys-libs/libstdc++-v3-3.3.3-r1 failed. !!! Function src_compile, Line 169, Exitcode 2 !!! (no error message) Seems to be the same problem as seen on amd64... I added this line to the ebuild and it works now: replace-flags -mcpu=G5 -mtune=G5 but there might be other -mcpu types be affected, so I guess the solution to this problem in the ebuild would be similar to the solution for amd64. So maybe this works: if use ppc64 then setting="`get-flag mcpu`" [ ! -z "$setting" ] && filter flags -mcpu="${setting}" -mtune="${setting}" fi Markus
by the way: the error occured while bootstrapping... Markus
ahh .. yeah you can't use -mcpu=xxxx . -mtune=970 is effectively the same thing according to alanm. -mcpu is turning on some 32 bit flags and such I gather so that's why you don't want to use it It's a bug sure but a bug upstream that i don't think they are going to address.
stick a fork in it
