public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: Paul Koning <paulkoning@comcast.net>
Cc: Andrew Pinski <pinskia@gmail.com>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: Can't build Ada
Date: Fri, 25 Nov 2022 15:26:38 -0500	[thread overview]
Message-ID: <CAF1jjLsFmDTub_WwCneDkxf4_YhEEceLVU1HSitTb1yHYJMV+Q@mail.gmail.com> (raw)
In-Reply-To: <E66A9BF6-883B-4EC6-ACD9-C421A92B677F@comcast.net>

On Fri, Nov 25, 2022 at 3:09 PM Paul Koning via Gcc <gcc@gcc.gnu.org> wrote:
> But in any case, how does that relate to the error messages I got?  They don't seem to have anything to do with missing compilers, but rather with the use of language features too new for the available (downloadable) Gnat.

Generally speaking, the reason is that with a normal compiler build,
where build = host = target, gcc can build itself and then run the
newly built self to build the language runtimes.  So if you're using
gcc 5 to build gcc 12, you're actually not using gcc 5 for all that
much.  The new gcc 12 is used to build for instance libX.  With a
cross compiler, it's possible that the build != host, and so you can't
use the newly built GCC in your build environment to build the
language runtimes.  For instance, say your cross compiler is hosted on
Windows, but you are building it on Linux.  You can't run the newly
built gcc 12, so you have to use the original gcc 5 instead.  That's
why you have to start with a new native compiler, and then use that to
build the cross compiler.

  parent reply	other threads:[~2022-11-25 20:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 19:57 Paul Koning
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 [this message]
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=CAF1jjLsFmDTub_WwCneDkxf4_YhEEceLVU1HSitTb1yHYJMV+Q@mail.gmail.com \
    --to=nightstrike@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=paulkoning@comcast.net \
    --cc=pinskia@gmail.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).