public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Koning <paulkoning@comcast.net>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Can't build Ada
Date: Sat, 26 Nov 2022 10:48:24 -0500	[thread overview]
Message-ID: <338FD630-E757-4595-8282-652A12044393@comcast.net> (raw)
In-Reply-To: <1350173E-C2FA-48AB-BC59-BD516FBF15B9@googlemail.com>



> On Nov 25, 2022, at 3:46 PM, Iain Sandoe <idsandoe@googlemail.com> wrote:
> 
> 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.

Thanks all.

I tried that (#1) and got the same failure.  The trouble seems to be that the current sources have Ada2020 constructs in them and the available Gnat doesn't support that version.  The commit that introduces these (or some of them at least) is 91d68769419b from Feb 4, 2022.

So I'm guessing I'll have to do this in two parts, first build a newer but not-latest Gnat from a release that doesn't include the problematic constructs, then follow that by using the intermediate to build the current sources.

I wonder if this incompatibility was intentional.  If not it would be good for the Ada maintainers to fix these and ensure that the current code can still be built with the most recent public release of Gnat.  Conversely, if it is intentional, the documentation should be updated to explain how to build the current code.

	paul



  reply	other threads:[~2022-11-26 15:48 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 [this message]
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=338FD630-E757-4595-8282-652A12044393@comcast.net \
    --to=paulkoning@comcast.net \
    --cc=gcc@gcc.gnu.org \
    --cc=idsandoe@googlemail.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).