From: Arnaud Charlet <charlet@adacore.com>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: Pierre-Marie de Rodat <derodat@adacore.com>,
gcc-patches@gcc.gnu.org, Arnaud Charlet <charlet@adacore.com>
Subject: Re: r272976 - in /trunk/gcc/ada: ChangeLog ali.adb ...
Date: Thu, 05 Sep 2019 09:52:00 -0000 [thread overview]
Message-ID: <20190905095201.GA4638@adacore.com> (raw)
In-Reply-To: <20190905084404.GA1531@adacore.com>
> > Can someone please remind me in which repository I can find the GCC
> > prerequisites doc sources?
>
> Answering my own question: found it under gcc/doc/install.texi
>
> Working on it...
Just installed the following change on trunk, thanks again for your feedback!
2019-09-05 Arnaud Charlet <charlet@adacore.com>
* doc/install.texi: Update and clarify requirements to build GNAT.
Index: doc/install.texi
===================================================================
--- doc/install.texi (revision 275399)
+++ doc/install.texi (working copy)
@@ -270,13 +270,35 @@
@option{--disable-multilib}. Otherwise, you may encounter an error such as
@samp{fatal error: gnu/stubs-32.h: No such file}
-@item GNAT
+@item @anchor{GNAT-prerequisite}GNAT
-In order to build the Ada compiler (GNAT) you must already have GNAT
-installed because portions of the Ada frontend are written in Ada (with
-GNAT extensions.) Refer to the Ada installation instructions for more
-specific information.
+In order to build GNAT, the Ada compiler, you need a working GNAT
+compiler (GCC version 4.7 or later).
+This includes GNAT tools such as @command{gnatmake} and
+@command{gnatlink}, since the Ada front end is written in Ada and
+uses some GNAT-specific extensions.
+
+In order to build a cross compiler, it is strongly recommended to install
+the new compiler as native first, and then use it to build the cross
+compiler. Other native compiler versions may work but this is not guaranteed and
+will typically fail with hard to understand compilation errors during the
+build.
+
+Similarly, it is strongly recommended to use an older version of GNAT to build
+GNAT. More recent versions of GNAT than the version built are not guaranteed
+to work and will often fail during the build with compilation errors.
+
+Note that @command{configure} does not test whether the GNAT installation works
+and has a sufficiently recent version; if too old a GNAT version is
+installed and @option{--enable-languages=ada} is used, the build will fail.
+
+@env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables
+must not be set when building the Ada compiler, the Ada tools, or the
+Ada runtime libraries. You can check that your build environment is clean
+by verifying that @samp{gnatls -v} lists only one explicit path in each
+section.
+
@item A ``working'' POSIX compatible shell, or GNU bash
Necessary when running @command{configure} because some
@@ -2705,27 +2727,8 @@
@section Building the Ada compiler
-In order to build GNAT, the Ada compiler, you need a working GNAT
-compiler (GCC version 4.0 or later).
-This includes GNAT tools such as @command{gnatmake} and
-@command{gnatlink}, since the Ada front end is written in Ada and
-uses some GNAT-specific extensions.
+See @ref{GNAT-prerequisite}.
-In order to build a cross compiler, it is suggested to install
-the new compiler as native first, and then use it to build the cross
-compiler.
-
-@command{configure} does not test whether the GNAT installation works
-and has a sufficiently recent version; if too old a GNAT version is
-installed, the build will fail unless @option{--enable-languages} is
-used to disable building the Ada front end.
-
-@env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables
-must not be set when building the Ada compiler, the Ada tools, or the
-Ada runtime libraries. You can check that your build environment is clean
-by verifying that @samp{gnatls -v} lists only one explicit path in each
-section.
-
@section Building with profile feedback
It is possible to use profile feedback to optimize the compiler itself. This
next prev parent reply other threads:[~2019-09-05 9:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190703081457.62952.qmail@sourceware.org>
2019-09-04 13:44 ` Maciej W. Rozycki
2019-09-04 13:55 ` Arnaud Charlet
2019-09-05 1:17 ` Maciej W. Rozycki
2019-09-05 7:20 ` Arnaud Charlet
2019-09-05 8:44 ` Arnaud Charlet
2019-09-05 9:52 ` Arnaud Charlet [this message]
2019-09-09 14:28 ` Christophe Lyon
2019-09-09 15:18 ` Arnaud Charlet
2019-09-09 15:24 ` Christophe Lyon
2019-09-10 10:17 ` Arnaud Charlet
2019-09-10 10:24 ` Christophe Lyon
2019-10-25 5:52 ` Gerald Pfeifer
2019-10-28 10:14 ` Arnaud Charlet
2019-10-28 10:31 ` Andreas Schwab
2019-11-05 11:46 ` Arnaud Charlet
2019-09-04 14:01 ` Andreas Schwab
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=20190905095201.GA4638@adacore.com \
--to=charlet@adacore.com \
--cc=derodat@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=macro@wdc.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).