[MacPorts] #62440: perl5: invalid SDK path hardcoded on macOS 11
MacPorts
noreply at macports.org
Sat Jun 26 20:55:20 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 mojca):
I just tested on macOS 11/arm64 and solely revbumping perl 5.32 (meaning
that `MacOSX11.sdk` gets hardcoded into `Config` files rather than
`MacOSX11.0.sdk`) leads to successful installation of p5.32-tk, for
example.
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`, ...
* we should not bake those values into build scripts
I totally agree with the second item, but at this very moment it's a tiny
bit non-trivial to achieve unless we also remove SDKs from all the
environmental variables.
I believe we should look at this from two completely different angles and
try to find:
* something that fixes the problem immediately
* something that fixes the problem correctly
At this moment I would like to solve the first one. We need to talk to
upstream to address the second one.
--
Ticket URL: <https://trac.macports.org/ticket/62440#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list