From: Iain Sandoe <idsandoe@googlemail.com>
To: Paul Koning <paulkoning@comcast.net>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Can't build Ada
Date: Fri, 25 Nov 2022 20:46:15 +0000 [thread overview]
Message-ID: <1350173E-C2FA-48AB-BC59-BD516FBF15B9@googlemail.com> (raw)
In-Reply-To: <CA+=Sn1mnC8W625tJX2LJmCcqxJqD7atRoDoEgC=oKs+7Bm2dcg@mail.gmail.com>
Hi Paul,
> On 25 Nov 2022, at 20:13, Andrew Pinski via Gcc <gcc@gcc.gnu.org> wrote:
>
> On Fri, Nov 25, 2022 at 12:08 PM Paul Koning <paulkoning@comcast.net> wrote:
>>
>>> On Nov 25, 2022, at 3:03 PM, Andrew Pinski <pinskia@gmail.com> wrote:
>>>
>>> On Fri, Nov 25, 2022 at 11:59 AM Paul Koning via Gcc <gcc@gcc.gnu.org> wrote:
>>>>
>>>> I'm trying to use fairly recent GCC sources (the gcc-darwin branch to be precise) to build Ada, starting with the latest (2020) release of Gnat from Adacore.
>>>
>>> Are you building a cross compiler or a native compiler?
>>> If you are building a cross, you need to bootstrap a native compiler first.
>>
>> I'm not sure. The installed Gnat is x86_64-darwin; I want to build aarch64-darwin.
>
> You have to build a x86_64-darwin compiler first with the same sources
> as you are building for aarch64-darwin.
So ..
1/ if you are on arm64 Darwin,
- the first step is to bootstrap the compiler using Rosetta 2 and the available x86_64 gnat.
2/ if you are on x86_64 Darwin…
- the first step is to bootstrap the compiler using the available x86-64 gnat.
then...
- then you can build a cross to aarch64 using that just-build compiler.
- then you can do a native cross (target==host!=build) using that, which will give you a usable native compiler for arm64 ..
(2 is what I was doing all the way through the development - until I recently got an arm64 machine)..
I know that Rosetta 2 bootstrap worked a few days ago …
BTW: the final step “native cross” can be a bit tricky in terms of configure line - since some configure steps cannot (in general) run the tools on the “foreign” host - so that you might need to specify the linker version (we don’t have the option to do —with-ld64=NN.MM yet, but there is code that cares about the version of ld64.. so)
>> But in any case, how does that relate to the error messages I got? They don't seem to have anything to do with missing compilers, but rather with the use of language features too new for the available (downloadable) Gnat.
>
> From https://gcc.gnu.org/install/prerequisites.html:
> "In order to build a cross compiler, it is strongly recommended to
> install the new compiler as native first, and then use it to build the
> cross compiler. Other native compiler versions may work but this is
> not guaranteed and *****will typically fail with hard to understand
> compilation errors during the build.****"
>
> I added the emphasis but yes this is all documented correctly.
thanks for the reminder!
cheers
Iain
next prev parent reply other threads:[~2022-11-25 20:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 19:57 Paul Koning
2022-11-25 20:03 ` Andrew Pinski
2022-11-25 20:08 ` Paul Koning
2022-11-25 20:13 ` Andrew Pinski
2022-11-25 20:46 ` Iain Sandoe [this message]
2022-11-26 15:48 ` Paul Koning
2022-11-26 15:58 ` Iain Sandoe
2022-11-26 16:27 ` Paul Koning
2022-11-26 16:42 ` Arnaud Charlet
2022-11-26 16:52 ` Iain Sandoe
2022-11-26 18:02 ` Paul Koning
2022-11-26 18:06 ` Paul Koning
2022-11-26 18:15 ` Iain Sandoe
2022-11-27 11:54 ` Iain Sandoe
2022-11-25 20:17 ` Iain Sandoe
2022-11-25 20:26 ` NightStrike
2022-11-25 20:45 ` Alexandre Oliva
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=1350173E-C2FA-48AB-BC59-BD516FBF15B9@googlemail.com \
--to=idsandoe@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=paulkoning@comcast.net \
/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).