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: Sat, 26 Nov 2022 16:52:36 +0000 [thread overview]
Message-ID: <DC3B1308-F75F-4DB3-BA44-9ACB6566D0EF@googlemail.com> (raw)
In-Reply-To: <3D25589F-2417-49B2-BB1A-7F0E6017880F@adacore.com>
> On 26 Nov 2022, at 16:42, Arnaud Charlet <charlet@adacore.com> wrote:
>
>
>>> The current statement (https://gcc.gnu.org/install/prerequisites.html) is:
>>>
>>> GNAT
>>> In order to build GNAT, the Ada compiler, you need a working GNAT compiler (GCC version 5.1 or later).
>>>
>>> so, if 5.1 is not working, then perhaps a PR is in order.
>>
>> I will do that, if the "shell in Rosetta" thing doesn't cure the problem.
>
> You won’t need to, the version of gnat you are using is recent enough, you need to follow Ian’s instructions to the letter. The Ada 2022 code is a red herring and is only problematic when you build a cross with a non matching native, not when building a native compiler.
One additional question/point - which branch are you trying to build the cross from?
I am sure it will not work from upstream master.
Unfortunately, owing to lack of free time… aarch64-darwin is not yet completely ready to upstream, so folks are using the development branch here: https://github.com/iains/gcc-darwin-arm64 (which I will update later, based on the master version mentioned earlier; if testing goes OK).
Iain.
next prev parent reply other threads:[~2022-11-26 16:52 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 [this message]
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=DC3B1308-F75F-4DB3-BA44-9ACB6566D0EF@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).