From: Serge Belyshev <belyshev@depni.sinp.msu.ru>
To: Jeff Law <jeffreyalaw@gmail.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: PING^2: [PATCH] Add --enable-first-stage-cross configure option
Date: Wed, 13 Jul 2022 12:35:56 +0300 [thread overview]
Message-ID: <87h73ls6bn.fsf@depni.sinp.msu.ru> (raw)
In-Reply-To: <7e8e6f89-75ea-a758-b430-fbbd01127768@gmail.com> (Jeff Law via Gcc-patches's message of "Sat, 9 Jul 2022 21:13:30 -0600")
Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
> 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
Oh, I did not know that "make install-gcc install-target-libgcc" works in this case.
So in the end, patch simplifies quirky first stage cross tool build procedure from
configure --target=$target --enable-languages=c --disable-threads --disable-shared # plus --with-newlib when --with-sysroot=
make all-gcc all-target-libgcc
make install-gcc install-target-libgcc
to
configure --target=$target --enable-first-stage-cross
make
make install
Either way is more or less okay for me, it just needs to be documented.
prev parent reply other threads:[~2022-07-13 9:36 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 ` PING^2: " Jeff Law
2022-07-13 9:35 ` Serge Belyshev [this message]
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=87h73ls6bn.fsf@depni.sinp.msu.ru \
--to=belyshev@depni.sinp.msu.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@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).