https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #16 from Stas Sergeev ---
(In reply to Jonathan Wakely from comment #15)
> For the record, this has moved to
> https://gcc.gnu.org/ml/gcc-help/2019-10/msg2.html
Thanks, I also would like to apologize to Joseph for
not following
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #15 from Jonathan Wakely ---
For the record, this has moved to
https://gcc.gnu.org/ml/gcc-help/2019-10/msg2.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
Stas Sergeev changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #13 from joseph at codesourcery dot com ---
On Wed, 25 Sep 2019, stsp at users dot sourceforge.net wrote:
> Unfortunately I wasn't able to fully understand the
> idea you explain. You mention "sysroot" and "non-sysroot"
> builds,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #12 from Stas Sergeev ---
(In reply to jos...@codesourcery.com from comment #11)
> Those -isystem paths are the *non-sysroot* kind of paths for headers for a
> cross compiler.
Unfortunately I wasn't able to fully understand the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #11 from joseph at codesourcery dot com ---
Those -isystem paths are the *non-sysroot* kind of paths for headers for a
cross compiler.
There is no support for building a *non-sysroot* cross toolchain when its
libc is installed in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879
--- Comment #10 from Stas Sergeev ---
(In reply to Jonathan Wakely from comment #9)
> It's possible the paths passed to -isystem should be prefixed with = when a
> sysroot is in use,
Great idea! Maybe it can even be unconditional,
as w/o
