[MacPorts] #53244: wine, wine-devel install but don't work

MacPorts noreply at macports.org
Fri Jan 20 02:10:12 UTC 2017


#53244: wine, wine-devel install but don't work
------------------------------+------------------------
  Reporter:  philroberts      |      Owner:  ryandesign
      Type:  defect           |     Status:  assigned
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.3.5
Resolution:                   |   Keywords:
      Port:  wine wine-devel  |
------------------------------+------------------------

Comment (by ryandesign):

 pkgconfig is a build tool. It doesn't matter whether it is installed
 universal or not; the wine build system simply calls the `pkg-config`
 binary and it says what flags to use to link with other libraries.

 I don't find the distinction of building from source vs. building from a
 binary package to be particularly relevant. After all, what do you think
 the buildbots are doing when a binary package is not available? They're
 building from source and then making the result available as a binary
 package.

 One possibility that seems unlikely to me is that some port builds itself
 differently on different CPUs, and that when it is built on the buildbot,
 it is built in a way that only works on the specific CPU that's in the
 buildbot systems (which are Xserve3,1 with Xeon E5520 or X5520 CPUs), and
 that the binary that's produced will fail to work on other CPUs. The only
 port I know of in wine's dependency chain that's like that is gmp, and it
 already contains a directive that ensures it will build from source on
 your system and will not use a binary (see #41614). If there is another
 port like that, we can add that directive to that port too.

 Another perhaps more likely possibility is that some port's library API or
 ABI changed in an incompatible way, but the authors of the library didn't
 indicate that by increasing the library's major version number, so we
 didn't know that we had to rebuild all ports using the library. If they
 had changed the major version number, rev-upgrade would have immediately
 noticed that things needed to be rebuilt against the new library.

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


More information about the macports-tickets mailing list