RE: Treat GCC cross compiler as a native compiler?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



“cross-native” toolchain should be called canadian toolchain.


Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

From: Richard Sandiford<mailto:richard.sandiford@xxxxxxx>
Sent: Wednesday, June 29, 2022 03:44
To: unlvsur unlvsur via Gcc-help<mailto:gcc-help@xxxxxxxxxxx>
Cc: unlvsur unlvsur<mailto:unlvsur@xxxxxxxx>
Subject: Re: Treat GCC cross compiler as a native compiler?

unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx> 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





[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux