From: John Henning <john.henning@oracle.com>
To: Jeff Law <jeffreyalaw@gmail.com>, Qing Zhao <qing.zhao@oracle.com>
Cc: Gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch][doc][PR101843]clarification on building gcc and binutils together
Date: Thu, 23 Sep 2021 11:07:07 +0000 [thread overview]
Message-ID: <4934BC81-E36E-4F81-81A5-F5733F5AC22B@oracle.com> (raw)
In-Reply-To: <e64cc2b1-20c5-ec91-197a-bf60ab908955@gmail.com>
Hello Jeff,
> I would strongly recommend removing all the documentation related to
> single tree builds.
Two questions:
(1) When you say "all", are you suggesting that in-the-gcc-tree builds of gmp, mpfr, mpc, and isl should no longer be documented? Or only in-tree builds of binutils?
(2) Is there any truth to the suggestion (found in some google tracks) that when building a cross-compiler, it is easier to build binutils in the same tree? For example
https://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc
https://www.gnu.org/software/gcc/simtest-howto.html
https://stackoverflow.com/a/6228588
It is out of respect for existing user habit that I proposed merely demoting it to an "alternative" method (while "recommending" the separate build).
-john
prev parent reply other threads:[~2021-09-23 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 22:27 Qing Zhao
2021-08-23 5:45 ` Jeff Law
2021-09-09 15:05 ` Qing Zhao
2021-09-19 16:57 ` Jeff Law
2021-09-23 11:07 ` John Henning [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=4934BC81-E36E-4F81-81A5-F5733F5AC22B@oracle.com \
--to=john.henning@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=qing.zhao@oracle.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).