https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90379
Iain Sandoe <iains at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2019-05-08 Ever confirmed|0 |1 --- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> --- I can repeat this on gcc122, but it's not clear what's different about this darwin-specific case that doesn't fire on others. It's reasonable that a linux host should apply darwin-specific fixes for a darwin cross, when the sysroot/SDK is darwin. What seems surprising is that the fixes are attempted when the target is not Darwin and the "sysroot" is /. However, not sure what the behaviour is supposed to be, officially.