From: Iain Sandoe <idsandoe@googlemail.com>
To: Paul Koning <paulkoning@comcast.net>
Cc: Andrew Pinski <pinskia@gmail.com>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: Can't build Ada
Date: Fri, 25 Nov 2022 20:17:52 +0000 [thread overview]
Message-ID: <47E1EABC-C5CB-4A4E-AB00-C06D74500313@googlemail.com> (raw)
In-Reply-To: <E66A9BF6-883B-4EC6-ACD9-C421A92B677F@comcast.net>
Hi Paul,
> On 25 Nov 2022, at 20:08, Paul Koning via Gcc <gcc@gcc.gnu.org> 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 are building a cross then.
> 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.
Building a cross GNAT requires that the build compiler is from the same sources as the cross - so, as Andrew says, you need to bootstrap the current sources on x86_64 and then use that compiler to build the cross to aarch64. I’m not sure exactly where this constraint is mentioned .. but, nevertheless, it is a constraint.
FWIW: I have not done this for a few weeks (using my arm64 prototype branch) but it was working fine then.
Iain
next prev parent reply other threads:[~2022-11-25 20:17 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
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 [this message]
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=47E1EABC-C5CB-4A4E-AB00-C06D74500313@googlemail.com \
--to=idsandoe@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=paulkoning@comcast.net \
--cc=pinskia@gmail.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).