From: Paul Koning <paulkoning@comcast.net>
To: GCC Development <gcc@gcc.gnu.org>
Subject: Can't build Ada
Date: Fri, 25 Nov 2022 14:57:31 -0500 [thread overview]
Message-ID: <2840BB68-0E3A-4848-AA39-32E9B822A4F0@comcast.net> (raw)
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.
It fails for several reasons. One is that two source files use [ ] for array initializer brackets when ( ) is apparently supposed to be used instead. Once I fix that, I get a pile of messages I don't know what to do about:
s-imagei.ads:95:11: declare_expression is an Ada 2020 feature
s-valueu.ads:152:09: declare_expression is an Ada 2020 feature
s-valueu.ads:160:09: declare_expression is an Ada 2020 feature
s-valueu.ads:184:06: "Subprogram_Variant" is not a valid aspect identifier
s-valuei.ads:80:11: declare_expression is an Ada 2020 feature
s-valuei.ads:95:08: declare_expression is an Ada 2020 feature
s-valuei.ads:141:06: "Subprogram_Variant" is not a valid aspect identifier
s-widthu.ads:84:09: declare_expression is an Ada 2020 feature
s-widthu.ads:93:11: run-time library configuration error
s-widthu.ads:93:11: file s-imgint.ads had parser errors
s-widthu.ads:93:11: entity "System.Img_Int.Image_Integer" not available
compilation abandoned
make[2]: *** [ada/contracts.o] Error 1
Given that the current open source Gnat is from 2020, so (apparently) it doesn't support Ada 2020 features, how is someone supposed to build the current GCC? I looked in the prerequisites listing on the webpage, but it says that the Gnat that is built on GCC 5.1 is sufficient. That seems to be wrong; the GCC in Gnat 2020 is 8.4.1 and it is apparently too old to work.
paul
next reply other threads:[~2022-11-25 19:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 19:57 Paul Koning [this message]
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
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=2840BB68-0E3A-4848-AA39-32E9B822A4F0@comcast.net \
--to=paulkoning@comcast.net \
--cc=gcc@gcc.gnu.org \
/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).