[MacPorts] #65939: libunwind: do not force +universal on <11, perhaps?

MacPorts noreply at macports.org
Sun Nov 5 18:16:19 UTC 2023


#65939: libunwind: do not force +universal on <11, perhaps?
---------------------------+-------------------------------------------
  Reporter:  barracuda156  |      Owner:  jeremyhu
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.7.2
Resolution:                |   Keywords:  powerpc, snowleopard, rosetta
      Port:  libunwind     |
---------------------------+-------------------------------------------

Comment (by ryandesign):

 Replying to [comment:3 mouse07410]:
 > Please-please-please, **drop** the ~~stupid~~ default {{{+universal}}}.
 It makes absolutely no sense now.
 >
 > ''This comment applies to the majority of the ports, if not to all of
 them.''

 The majority of ports do not enable the universal variant by default. Only
 an extremely small subset of ports default to the universal variant and
 they do so for specific presumably good reasons.

 The reason why libunwind does this is because it is a depedency of libcxx,
 as explained by [changeset:f7e9bbd6a7df0873a34a1b7c4a477b85dc1d511b
 /macports-ports the commit that first enabled it]. The idea, presumably,
 was that someone might install libcxx, and all ports would then
 automatically use that libcxx even if no dependency had been declared,
 meaning that normal MacPorts functionality for ensuring dependencies had
 the right architectures would not take effect, so it was necessary to
 ensure that libcxx and all of its dependencies had all possible
 architectures.

 In fact, the libcxx port doesn't install anything on 10.7 and later since
 the OS already includes it so perhaps defaulting to universal is not
 needed for these ports on 10.7 and later.

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


More information about the macports-tickets mailing list