[MacPorts] #62440: perl5: invalid SDK path hardcoded on macOS 11
MacPorts
noreply at macports.org
Sat Jun 26 21:09:44 UTC 2021
#62440: perl5: invalid SDK path hardcoded on macOS 11
---------------------------+----------------------
Reporter: chrstphrchvz | Owner: mojca
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: perl5 |
---------------------------+----------------------
Comment (by kencu):
Replying to [comment:9 mojca]:
> Ken, one part that I'm not sure about when reading your answer: are you
(and Jeremy) saying that:
> * we should never pass any SDK to `CFLAGS`, `LDFLAGS`, ... (apparently
the base does exactly that)
For anything to do with clang or Xcode, we are supposed to set SDKROOT and
leave the isysroot stuff out of the flags.
It might be that there are considered to be too many fringe cases to allow
this, like maybe nasm and such. I don't know if all those fringe compilers
respect SDKROOT.
> * or that we should not bake those values into build scripts
We can all see that we have undergone no end of significant troubles by
baking an SDK path into various installed scripts, and later the SDK path
changes.
But we have talked about this for literally years now, and it seems that
we can't stop doing it. Or maybe the software can't stop doing it, and we
can't find a way to stop the software from doing it, not sure which.
--
Ticket URL: <https://trac.macports.org/ticket/62440#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list