[MacPorts] #57802: muniversal PG could use $prefix/bin/lipo and $prefix/bin/libtool if available

[MacPorts]

#57802: muniversal PG could use $prefix/bin/lipo and $prefix/bin/libtool if
available
---------------------+-----------------------
  Reporter:  RJVB    |      Owner:  (none)
      Type:  defect  |     Status:  new
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:
Resolution:          |   Keywords:  has_patch
      Port:          |
---------------------+-----------------------
Changes (by RJVB):

 * keywords:   => has_patch


Old description:

> Using macports-clang versions newer than the host's AppleClang (clang
> from Xcode) you can end up with binaries that the host's lipo (and
> presumably libtool) command won't know how to handle. Example: static
> libraries from `-flto=thin` builds with clang-mp-5+ on OS X 10.9 .
>
> The lipo command from port:cctools has no problems with those files.
>
> You'd probably want to use the version from port:cctools only when a
> macports clang compiler is used, that should prevent reproducible build
> violations.

New description:

 Using macports-clang versions newer than the host's AppleClang (clang from
 Xcode) you can end up with binaries that the host's lipo (and presumably
 libtool) command won't know how to handle. Example: static libraries from
 `-flto=thin` builds with clang-mp-5+ on OS X 10.9 .

 The lipo command from port:cctools has no problems with those files.

 You'd probably want to use the version from port:cctools only when a
 macports clang compiler is used, that should prevent reproducible build
 violations, as in the attached (quick and dirty) patch.

--

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