Christer Solskogen via Gcc-help kirjoitti 12.2.2023 klo 19.51:
While cross compiling gcc with musl I see this:
checking for exported symbols... /home/solskogen/gcc/libcc1/configure:
line 15053: -T: command not found
yes
checking for -rdynamic... /home/solskogen/gcc/libcc1/configure: line
15063: -T: command not found
no
checking for library containing dlopen... none required
checking for -fPIC -shared... yes
configure: error:
Building GCC with plugin support requires a host that supports
-fPIC, -shared, -ldl and -rdynamic.
make[1]: *** [Makefile:11890: configure-libcc1] Error 1
This is the configure line: /home/solskogen/gcc/configure
--prefix=/usr --libexecdir=/lib --host=aarch64-centrix-linux-musl
--target=aarch64-centrix-linux-musl --build=x86_64-pc-linux-gnu
What is intersting in this case is WHICH GCC the build tries to use when
compiling libgcc. It should be the 'aarch64-centrix-linux-musl' targeted
cross-GCC, used for the becoming $host
system to create the executables and libraries for it. So what are the
CC_FOR_TARGET, GCC_FOR_TARGET, CXX_FOR_TARGET and GXX_FOR_TARGET in the
main Makefile and in the one
used for libgcc? My habit has been years to define these in environment
before running configure. Maybe these simply don't work in the "native
Canadian Cross" case. (To create a native
GCC with a cross-GCC).
