From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: PING^2: [PATCH] Add --enable-first-stage-cross configure option
Date: Sat, 9 Jul 2022 21:13:30 -0600 [thread overview]
Message-ID: <7e8e6f89-75ea-a758-b430-fbbd01127768@gmail.com> (raw)
In-Reply-To: <87tuec8usd.fsf_-_@depni.sinp.msu.ru>
On 1/9/2022 2:26 PM, 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.
>
> Usage example as a patch to glibc's scripts/build-many-libcs.py:
>
> diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
> index 580d25e8ee..3a6a7be76b 100755
> --- a/scripts/build-many-glibcs.py
> +++ b/scripts/build-many-glibcs.py
> @@ -1446,17 +1446,7 @@ class Config(object):
> # required to define inhibit_libc (to stop some parts of
> # libgcc including libc headers); --without-headers is not
> # sufficient.
> - cfg_opts += ['--enable-languages=c', '--disable-shared',
> - '--disable-threads',
> - '--disable-libatomic',
> - '--disable-decimal-float',
> - '--disable-libffi',
> - '--disable-libgomp',
> - '--disable-libitm',
> - '--disable-libmpx',
> - '--disable-libquadmath',
> - '--disable-libsanitizer',
> - '--without-headers', '--with-newlib',
> + cfg_opts += ['--enable-first-stage-cross',
> '--with-glibc-version=%s' % self.ctx.glibc_version
> ]
> cfg_opts += self.first_gcc_cfg
>
> Bootstrapped/regtested on x86_64-pc-linux-gnu, and
> tested with build-many-glibcs.py with the above patch.
>
> OK for mainline?
>
>
> ChangeLog:
>
> * configure.ac: Add --enable-first-stage-cross.
> * configure: Regenerate.
>
> gcc/ChangeLog:
>
> * doc/install.texi: Document --enable-first-stage-cross.
I'm not really sure we need a patch for this. Isn't it sufficient to
"make all-gcc && make all-target-libgcc"? Folks have been doing that
for decades.
Jeff
next prev parent reply other threads:[~2022-07-10 3:13 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
2022-01-16 21:13 ` PING^3: " Serge Belyshev
2022-07-10 3:13 ` Jeff Law [this message]
2022-07-13 9:35 ` PING^2: " 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=7e8e6f89-75ea-a758-b430-fbbd01127768@gmail.com \
--to=jeffreyalaw@gmail.com \
--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).