This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RFC: Extending --with-advance-toolchain to aarch64

From: Florian Weimer <fweimer at redhat dot com>
To: Steve Ellcey <sellcey at marvell dot com>
Cc: "gcc\@gcc.gnu.org" <gcc at gcc dot gnu dot org>, "tuliom\@linux.ibm.com" <tuliom at linux dot ibm dot com>
Date: Fri, 11 Oct 2019 10:28:50 +0200
Subject: Re: RFC: Extending --with-advance-toolchain to aarch64
References: <dd6757ea29019f93720d348db7b810ea3e8cbe07.camel@marvell.com> <87a7a8mu2k.fsf@oldenburg2.str.redhat.com> <57692cef07f22523391e395897acc5129c0c9c6c.camel@marvell.com>

* Steve Ellcey:

> I am not sure, but my guess is that it is because I am building
> binutils (including ld) using --with-sysroot.

That could be the case.  I guess there are two conflicting use cases for
sysroots, one where you want to mangle run-time paths to confine things
to the sysroot, and one where the run-time paths are different from the
sysroot paths (so it's more like a cross-compiler, even if the target is
native).

Thanks,
Florian

References:
- RFC: Extending --with-advance-toolchain to aarch64
  - From: Steve Ellcey
- Re: RFC: Extending --with-advance-toolchain to aarch64
  - From: Florian Weimer
- Re: RFC: Extending --with-advance-toolchain to aarch64
  - From: Steve Ellcey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]