public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: unlvsur unlvsur via Gcc-help <gcc-help@gcc.gnu.org>
Cc: unlvsur unlvsur <unlvsur@live.com>
Subject: Re: Treat GCC cross compiler as a native compiler?
Date: Wed, 29 Jun 2022 08:44:38 +0100	[thread overview]
Message-ID: <mptwnczvrq1.fsf@arm.com> (raw)
In-Reply-To: <DM6PR05MB469797483A011E4E2B893045D6BB9@DM6PR05MB4697.namprd05.prod.outlook.com> (unlvsur unlvsur via Gcc-help's message of "Wed, 29 Jun 2022 03:53:46 +0000")

unlvsur unlvsur via Gcc-help <gcc-help@gcc.gnu.org> writes:
> I want to make –host=aarch64-linux-musl –target=aarch64-linux-android to be a native compiler instead of just a cross compiler for aarch64-linux-android. Is that possible? (Since use aarch64-linux-android as host is difficult due to issues with -fPIC to stderr)

No, I don't think this is possible.  The usual definition of
"native compiler" is that the host and target are (exactly) the same.

It's possible (but difficult) to build a cross-native toolchain,
(build!=host, host==target).

Thanks,
Richard

  reply	other threads:[~2022-06-29  7:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  3:53 unlvsur unlvsur
2022-06-29  7:44 ` Richard Sandiford [this message]
2022-06-29 15:15   ` unlvsur unlvsur
2022-06-29 16:59     ` Segher Boessenkool
2022-06-29 17:03       ` unlvsur unlvsur
2022-06-29 17:52         ` Segher Boessenkool
2022-06-29 17:58           ` unlvsur unlvsur

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=mptwnczvrq1.fsf@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=unlvsur@live.com \
    /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).