* PING Re: [Patch][doc][PR101843]clarification on building gcc and binutils together
@ 2021-10-14 15:52 John Henning
2021-10-14 23:51 ` Jeff Law
0 siblings, 1 reply; 2+ messages in thread
From: John Henning @ 2021-10-14 15:52 UTC (permalink / raw)
To: Jeff Law; +Cc: Gcc-patches
Hi Jeff, not sure what you mean by "all", please can you clarify?
On 9/23/21, 7:08 AM, "Gcc-patches on behalf of John Henning via Gcc-patches" <gcc-patches-bounces+john.henning=oracle.com@gcc.gnu.org on behalf of gcc-patches@gcc.gnu.org> wrote:
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: PING Re: [Patch][doc][PR101843]clarification on building gcc and binutils together
2021-10-14 15:52 PING Re: [Patch][doc][PR101843]clarification on building gcc and binutils together John Henning
@ 2021-10-14 23:51 ` Jeff Law
0 siblings, 0 replies; 2+ messages in thread
From: Jeff Law @ 2021-10-14 23:51 UTC (permalink / raw)
To: John Henning; +Cc: Gcc-patches
On 10/14/2021 9:52 AM, John Henning wrote:
> Hi Jeff, not sure what you mean by "all", please can you clarify?
Anything related to single tree builds needs to be removed.
>
> On 9/23/21, 7:08 AM, "Gcc-patches on behalf of John Henning via Gcc-patches" <gcc-patches-bounces+john.henning=oracle.com@gcc.gnu.org on behalf of gcc-patches@gcc.gnu.org> wrote:
>
> 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?
gmp, mpfr, mpc and isl are requirements for building gcc and are not
germane to this discussion.
binutils is not a requirement for building gcc and any documentation
related to single tree builds using binutils, gdb & friends that are not
strictly needed to build gcc should be removed.
>
> (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 used to be easier when Cygnus kept those bits working. There's
enough divergence across the projects these days that it's easier to
build them separately and independently. It's been that way for, I'd
guess 15-20 years now.
>
> It is out of respect for existing user habit that I proposed merely demoting it to an "alternative" method (while "recommending" the separate build).
That existing user habit needs to be broken :-)
jeff
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-10-14 23:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-14 15:52 PING Re: [Patch][doc][PR101843]clarification on building gcc and binutils together John Henning
2021-10-14 23:51 ` Jeff Law
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).