[MacPorts] #62440: perl5: invalid SDK path hardcoded on macOS 11

MacPorts noreply at macports.org
Sat Jun 26 22:06:30 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):

 Replying to [comment:10 kencu]:
 > For anything to do with clang or Xcode, I believe we are supposed to set
 SDKROOT and try to leave the isysroot stuff out of the flags.

 Except that `isysroot` was added by Jeremy in
 [changeset:"8863962b79c56323bb4a6f9176b41844b6eeed75/macports-ports"
 8863962b perl5 pg: use correct sdkroot] to fix #59131 and #59154?

 It's possible that something either was or still is added by
 `portconfigure.tcl`, at least on >= darwin19.

 > We do see troubles when baking an SDK path into various installed
 scripts, and later the SDK path changes.

 Sure, we need to avoid this.

 > It seems to me that there is often no advantage to burning in these
 paths, and we might do best to leave them out.

 I totally agree. I'm just saying that it's a tiny bit non-trivial to
 remove them all out from `Config.pm` and `Config_heavy.pl` without
 upstream helping at least a bit.
 To me, by far the easiest solution seem to be removing them from
 environmental variables before building perl itself. I'm just not sure if
 I'm allowed to do that.

-- 
Ticket URL: <https://trac.macports.org/ticket/62440#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list