Kai Ruottu kirjoitti 18.1.2024 klo 14.39:
The prerequisites in your case are aworking compiler for
the'x86_64-linux' build system and a working cross-compiler from the
build/host 'x86_64-linux' system to the target 'x86_64-nacl-linux'
system. Whether the GCC configure scripts could quess what tools the
build should use for the $host and $target I have no clue. Years I
have always defined these with the : AR=<something> \ CC= <something>
\ CXX=<something> \ .... RANLIB=<something> \ for the $host system.
And : AR_FOR_TARGET=<something> \ CC_FOR_TARGET= <something> \
CXX_FOR_TARGET=<something> \ .... RANLIB_FOR_TARGET=<something> \ for
the $target system. Similarly for the $build system with the :
<TOOL>_FOR_BUILD=<something> rows in the script used as the
configure command, before the final 'configure' command in it.
Not much left to guess...
Should I now shoot Thunderbird because it decided to change my written
text to something unreadable?
Later text then surprisingly wasn't changed :
The already existing cross-compiler for the $target should be
used to compile all the usual target libraries like 'libgcc' during
the build. But they already were built during the cross-compiler
build so producing them once again is basically "reinventing the
wheel". So using the command :
