From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "R. Diez" <rdiezmail-gcc@yahoo.de>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Specifying where Binutils is and what it is called
Date: Mon, 20 Apr 2020 09:47:28 +0100 [thread overview]
Message-ID: <CAH6eHdRW4OT7fN5ZqEYAEOdL_82ZgKRDgPTcYpByroCaet88CA@mail.gmail.com> (raw)
In-Reply-To: <590749852.1515706.1587371249089@mail.yahoo.com>
On Mon, 20 Apr 2020 at 09:27, R. Diez wrote:
>
> > That seems like an unnecessary worry. Why would the
> > phase 1 compiler install *more* than the final one?
>
> That is a very bold claim to make. GCC is a complex beast. Are you sure about that? Is there any test case for it? How about in the future? What if only need the C compiler to build Newlib, but the final toolchain only needs the C++ compiler, in order to reduce the total toolchain build time and save space in my final container?
So delete the cc1 executable after installation. That's not hard.
next prev parent reply other threads:[~2020-04-20 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <590749852.1515706.1587371249089.ref@mail.yahoo.com>
2020-04-20 8:27 ` R. Diez
2020-04-20 8:47 ` Jonathan Wakely [this message]
[not found] <238241866.1719021.1587558240444.ref@mail.yahoo.com>
2020-04-22 12:24 ` R. Diez
2020-04-23 8:24 ` Christer Solskogen
[not found] <2007965762.1537196.1587376378163.ref@mail.yahoo.com>
2020-04-20 9:52 ` R. Diez
[not found] <921250919.1086849.1587309283539.ref@mail.yahoo.com>
2020-04-19 15:14 ` R. Diez
2020-04-19 18:49 ` Jonathan Wakely
2020-04-20 5:25 ` Kai Ruottu
2020-04-20 5:32 ` Kai Ruottu
2020-04-20 18:55 ` Jim Wilson
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=CAH6eHdRW4OT7fN5ZqEYAEOdL_82ZgKRDgPTcYpByroCaet88CA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rdiezmail-gcc@yahoo.de \
/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).