https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85869
Arnd Bergmann <arnd at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|build |
Target|x86_64-*-*, i?86-*-* |
Host|powerpc64le |
Build|x86_64-*-* |
--- Comment #2 from Arnd Bergmann <arnd at linaro dot org> ---
Ah, found a bug in my scripts: I had built and installed a i386 cross compiler
from these sources, but passed the wrong PATH variable, so it picked up a
native compiler of the wrong version instead. This works fine now after fixing
my script, sorry about the false-positive report.
A related problem still seems to happen for the
build=x86_64/host=ppc64le/target=x86_64 cross compiler when building the 32-bit
libgcc: I have the correct x86_64-linux-gcc binary in the PATH here, and this
gets used for the 64-bit libgcc, but when building the 32-bit libgcc, it uses
'cc -m32' instead, which comes from /usr/bin/.
After manually removing the '/usr/bin/cc -> gcc' symlink, that appears to work
fine as well, but I don't see why that symlink causes this behavior.
