public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Serge Belyshev <belyshev@depni.sinp.msu.ru>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: PING^2: [PATCH] Add --enable-first-stage-cross configure option
Date: Mon, 10 Jan 2022 15:10:17 +0000	[thread overview]
Message-ID: <YdxMWSo6I13nusjt@redhat.com> (raw)
In-Reply-To: <87tuec8usd.fsf_-_@depni.sinp.msu.ru>

On 10/01/22 00:26 +0300, Serge Belyshev wrote:
>Ping: [PATCH] Add --enable-first-stage-cross configure option
>https://gcc.gnu.org/pipermail/gcc-patches/2021-July/575318.html
>
>
>Add --enable-first-stage-cross configure option
>
>Build static-only, C-only compiler that is sufficient to cross compile
>glibc.  This option disables various runtime libraries that require
>libc to compile, turns on --with-newlib, --without-headers,
>--disable-decimal-float, --disable-shared, --disable-threads, and sets
>--enable-languages=c.

>Rationale: current way of building first stage compiler of a cross
>toolchain requires specifying a list of target libraries that are not
>going to be compiled due to their dependency on target libc.  This
>list is not documented in gccinstall.texi and sometimes changes.  To
>simplify the procedure, it is better to maintain that list in the GCC
>itself.

I think this is a great idea.

I don't think it makes any difference to this patch, but I've just
committed a change to libstdc++ so that you no longer neeed to add
--with-newlib when libstdc++ is configured with --without-headers
(because it's counter-intuitive to have to say which libc you're using
when not using any libc).

I only tested it for --disable-hosted-libstdcxx --without-headers
because I am not sure what libstdc++ even does if you build it hosted
but --without-headers.


  reply	other threads:[~2022-01-10 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 13:39 Serge Belyshev
2021-09-06 13:13 ` Ping: " Serge Belyshev
2022-01-09 21:26   ` PING^2: " Serge Belyshev
2022-01-10 15:10     ` Jonathan Wakely [this message]
2022-01-16 21:13     ` PING^3: " Serge Belyshev
2022-07-10  3:13     ` PING^2: " Jeff Law
2022-07-13  9:35       ` Serge Belyshev

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=YdxMWSo6I13nusjt@redhat.com \
    --to=jwakely@redhat.com \
    --cc=belyshev@depni.sinp.msu.ru \
    --cc=gcc-patches@gcc.gnu.org \
    /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).