From: Christer Solskogen <christer.solskogen@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Problem cross-compiling gcc
Date: Mon, 13 Feb 2023 09:35:56 +0100 [thread overview]
Message-ID: <tscspd$173k$1@ciao.gmane.io> (raw)
In-Reply-To: <20230213081617.GC25951@gate.crashing.org>
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. In fact, cross compiling gcc is
pretty good way to check that the cross compiler is in good shape.
--
chs
next prev parent reply other threads:[~2023-02-13 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 17:51 Christer Solskogen
2023-02-12 19:24 ` Jonathan Wakely
2023-02-13 7:19 ` Christer Solskogen
2023-02-13 8:37 ` Christer Solskogen
2023-02-12 20:01 ` Kai Ruottu
2023-02-13 7:23 ` Christer Solskogen
2023-02-13 10:30 ` Kai Ruottu
2023-02-13 8:16 ` Segher Boessenkool
2023-02-13 8:35 ` Christer Solskogen [this message]
2023-02-13 8:47 ` Segher Boessenkool
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='tscspd$173k$1@ciao.gmane.io' \
--to=christer.solskogen@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).