https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84744
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-04-23
Ever confirmed|0 |1
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Installing your own glibc in a new location and trying to point GCC to it with
-I /FaF/glibc/include is not "the default settings".
As has been explained, you need to rebuild GCC to use the new glibc. To do that
you also need the Linux kernel headers in the same sysroot tree, i.e.
/FaF/glibc
Did you try that yet?
