[MacPorts] #62440: perl5: invalid SDK path hardcoded on macOS 11
MacPorts
noreply at macports.org
Sun Jun 27 04:23:16 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 jmroot):
Replying to [comment:7 mojca]:
> * Is passing `/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk` in
fact needed in order build (any given) software correctly or is it there
"just in case"?
Not at present, but that will change as soon as Xcode starts defaulting to
using `MacOSX12.sdk`. And of course if a user wants to use any other non-
default SDK, you need to tell the toolchain about it.
> * I see that we are now passing `MacOSX11.sdk` to compiler flags (which
is just a symlink to `MacOSX11.x.sdk`), while this used to be
`MacOSX11.0.sdk` at the time when perl was built. Wouldn't thus this
problem be fixed without any further changes if we simply revbumped perl?
The problem would be hidden in the common case, sure.
--
Ticket URL: <https://trac.macports.org/ticket/62440#comment:13>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list