[MacPorts] #36438: ports which mirror system libraries can cause +universal ports to fail if they are -universal

[MacPorts]

#36438: ports which mirror system libraries can cause +universal ports to fail if
they are -universal
----------------------------+------------------------
  Reporter:  ahelfer1971@…  |      Owner:  jeremyhu@…
      Type:  defect         |     Status:  assigned
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.1.2
Resolution:                 |   Keywords:
      Port:  ld64           |
----------------------------+------------------------
Changes (by cal@…):

 * cc: cal@… (added)


Comment:

 Replying to [comment:36 rmstonecipher@…]:
 > Would making +universal a default variant for libstdcxx and other ports
 plagued by this problem be an acceptable solution?

 This would however require people to build a lot of universal code they
 might not want or need. I'd like to object this proposal.

 Replying to [comment:37 jeremyhu@…]:
 > {{{
 > /opt/local/lib $ for f in *; do [[ -f /usr/lib/$f ]] && port provides
 /opt/local/lib/$f; done | sed 's/.*: //' | sort -u
 > }}}

 This lists _all_ ports that provide libraries also shipped with OS X. Note
 that we only need to consider those that are being used without a
 dependency being specified. `zlib` or `kerberos5` are not affected,
 because ports using them should declare a dependency on them, which would
 cause MacPorts to ensure they are present in the required architecture(s).

 It seems we should rather find out why the linker is trying to use
 libstdc++. Is it an indirect dependency of something in the perl build
 process? Is it hard-coded into the ld64 source? While there are some
 hardcoded paths in the source, they point to /usr/lib and don't seem to
 cause this.

-- 
Ticket URL: <https://trac.macports.org/ticket/36438#comment:56>
MacPorts <http://www.macports.org/>
Ports system for OS X