On Mon, Feb 13, 2023 at 09:35:56AM +0100, Christer Solskogen via Gcc-help wrote: > On 13.02.2023 09:16, Segher Boessenkool wrote: > >On Sun, Feb 12, 2023 at 06:51:06PM +0100, Christer Solskogen via Gcc-help > >wrote: > >>While cross compiling gcc with musl I see this: > > > >>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 > >>--enable-languages=c,c++ --disable-multilib --enable-checking=release > >>--disable-nls --with-gcc-major-version-only --enable-plugin > >>--disable-libstdcxx-pch --enable-default-pie --enable-default-ssp > >>--disable-libsanitizer --enable-host-shared > > > >That is not a cross-compiler, you are building a cross-built native > >compiler here (host=target). To do that you already need a working > >cross-compiler, so it is probably not what you intended to do. > > > > Oh, I know. That's why the subject is "cross-compiling gcc" :-) > I already have a working cross compiler. Aha :-) > In fact, cross compiling gcc is > pretty good way to check that the cross compiler is in good shape. I'd say it is mainly a good way to hit problems no one else does. For example many things won't be detected correctly by the autoxxxx macros It's not helped by the fact that musl isn't very mainstream either of course, but I guess you are trying to change that :-) gl;hf, Segher
