public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Arnaud Charlet <charlet@adacore.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Arnaud Charlet <charlet@adacore.com>,
	gcc-patches@gcc.gnu.org, bernd.edlinger@hotmail.de
Subject: Re: [gcc r12-6398] [Ada] Reduce runtime dependencies on stage1
Date: Mon, 30 May 2022 08:40:08 +0000	[thread overview]
Message-ID: <20220530084008.GA211140@adacore.com> (raw)
In-Reply-To: <87wne7mibp.fsf@euler.schwinge.homeip.net>

> >  In order to build GNAT, the Ada compiler, you need a working GNAT
> > -compiler (GCC version 4.7 or later).
> > +compiler (GCC version 5.1 or later).
> >
> >  This includes GNAT tools such as @command{gnatmake} and
> >  @command{gnatlink}, since the Ada front end is written in Ada and
> 
> I've now tested that, but find that it doesn't work:
> 
>     [...]
>     gcc -c -g  -gnatpg -gnatwns -gnata -W -Wall -I- -I. -Iada/generated -Iada -I[...]/source-gcc/gcc/ada [...]/source-gcc/gcc/ada/contracts.adb -o ada/contracts.o

Ah, that's unfortunate. I guess on my side I'm using a version of GNAT built
without assertions, so not failing on this.

> So, what is actually the prerequisite GCC/Ada compiler version to be able
> to build GCC 12+ GCC/Ada?

I'm afraid I don't have more info at this stage, I assume GCC 6.1 would work
(not tested, if someone could confirm that would be great).

Arno

      reply	other threads:[~2022-05-30  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220110094108.2755D3891C1E@sourceware.org>
2022-01-18  9:48 ` Thomas Schwinge
2022-01-18 10:41   ` Arnaud Charlet
2022-01-18 10:46     ` Arnaud Charlet
2022-05-27  9:32       ` Thomas Schwinge
2022-05-30  8:40         ` Arnaud Charlet [this message]

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=20220530084008.GA211140@adacore.com \
    --to=charlet@adacore.com \
    --cc=bernd.edlinger@hotmail.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=thomas@codesourcery.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).