From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 121465 invoked by alias); 9 Sep 2019 14:28:09 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 121452 invoked by uid 89); 9 Sep 2019 14:28:09 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-8.8 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,GIT_PATCH_3,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=sk:armv8l, sk:armv8l-, 3300, verifying X-HELO: mail-lf1-f54.google.com Received: from mail-lf1-f54.google.com (HELO mail-lf1-f54.google.com) (209.85.167.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 09 Sep 2019 14:28:07 +0000 Received: by mail-lf1-f54.google.com with SMTP id u13so10654882lfm.9 for ; Mon, 09 Sep 2019 07:28:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mB9Gb3+93/G6g7aRQzivPqnf1J1XiK/vfLhKBFr1vI0=; b=XlkmjhYA4/Rx86S6I+5w9WWMnY6xcc7xTHrOoS78/8FF1AeaGKXvHtvWCwMGC47lX2 ot/oVG8z/7WcNUuqRN4zKzDBueGQuOxMA1l3ztyNDCnnmOVt1Lw+P5TVSJ2CjYqwkaJ4 j5dPr6ET8I42gXfX+fC6f1yGNcoRz4FHVcOjn5XLC0mUo/9MZmhXwy0gpZfrclopEgSw MF/uNPaqAT3sDOqJoP1Le/shl8EvH8TB71gazbvPwtNegR4H1I8S2E26iHKUUx7i5rv0 YbmaeZaWiGKL9/pTJP4GpemQJR5lLFwrq6ICU+sUDTrKdaS2qFRB0PHf4xl4wLHdybWk PxrA== MIME-Version: 1.0 References: <20190703081457.62952.qmail@sourceware.org> <20190904135528.GE13039@adacore.com> <20190905072001.GA21727@adacore.com> <20190905084404.GA1531@adacore.com> <20190905095201.GA4638@adacore.com> In-Reply-To: <20190905095201.GA4638@adacore.com> From: Christophe Lyon Date: Mon, 09 Sep 2019 14:28:00 -0000 Message-ID: Subject: Re: r272976 - in /trunk/gcc/ada: ChangeLog ali.adb ... To: Arnaud Charlet Cc: "Maciej W. Rozycki" , Pierre-Marie de Rodat , gcc Patches Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-09/txt/msg00527.txt.bz2 On Thu, 5 Sep 2019 at 11:52, Arnaud Charlet wrote: > > > > 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 > > * doc/install.texi: Update and clarify requirements to build GNAT. > Hi Arnaud, It seems there's a problem with this patch: /snapshots/gcc.git~master/gcc/doc/install.texi:2730: @ref reference to nonexistent node `GNAT-prerequisite' Makefile:3300: recipe for target '/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/gcc.git~master-stage2/gcc/HTML/gcc-10.0.0/gccinstall/index.html' failed Christophe > 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