public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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: Wed, 04 Sep 2019 13:55:00 -0000	[thread overview]
Message-ID: <20190904135528.GE13039@adacore.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1909032337010.18224@redsun52.ssa.fujisawa.hgst.com>

Maciej,

>  This change (not posted to `gcc-patches' for some reason) has caused a 
> regression in the form of a build failure with the `riscv-linux-gnu' 
> target (and for the record the `x86_64-linux-gnu' build/host running GCC 
> 8.3.0):
> 
> ali.adb:34:28: warning: use clause for package "GNAT" has no effect
> ali.adb:35:28: warning: use clause for package "Dynamic_HTables" has no effect
> ali.adb:155:52: "Bucket_Range_Type" is undefined (more references follow)
> ali.adb:158:27: "Dynamic_Hash_Tables" is undefined
> ali.adb:173:30: "Sig_Map" is undefined (more references follow)
> gnatmake: ".../gcc/ada/ali.adb" compilation error
> make[3]: *** [../gcc-interface/Makefile:469: gnatmake-re] Error 4
> make[3]: Leaving directory '.../gcc/ada/tools'
> make[2]: *** [Makefile:216: gnattools-cross] Error 2
> make[2]: Leaving directory '.../gnattools'
> make[1]: *** [Makefile:11224: all-gnattools] Error 2
> 
> -- that has persisted ever since.

As documented in https://gcc.gnu.org/install/build.html
you need a matching native GNAT compiler to build a GNAT cross compiler.

If I understood properly, you are using a GCC 8.3.0 as the host compiler
to build a GNAT cross compiler, which indeed won't work: you need to first
build a native matching compiler and then use this matching compiler to build
the cross.

Arno

  reply	other threads:[~2019-09-04 13:55 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 [this message]
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
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=20190904135528.GE13039@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).