https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105719
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iains at gcc dot gnu.org
--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #0)
> This is split off from bug 93082. Basically, if there is a header that needs
> to be fixincluded in /Systems/Library/Frameworks or /Library/Frameworks or
> ${SDKROOT}/Library/Frameworks, fixincludes currently won't find it. This
> should be fixed by adding another include tree (or trees) for fixincludes to
> search.
the way that header search works, you probably want to keep the sysroot (a.k.a
SDKROOT) distinct (you might want to look in gcc/config/darwin-c.cc for how the
eventual search paths are constructed, just for background).
Solving 37036 would also allow us to have multiple SDKs - which would be nice
since we can, in principle, target any version of Darwin with the same compiler
- the limitation preventing that is that the fixed includes (and SDK includes
used in some libraries) do not work over more than a few OS revisions ..
forcing us to need cross compilers for other OS versions in a rather artificial
way. If we could implement the OS version as a multilib we could avoid that
and just have one compiler to target any version (or the same arch, of course).
[dreams of things we might do if time were available]
