[MacPorts] #52337: atk build failed in macOS Sierra 10.12
MacPorts
noreply at macports.org
Sat Sep 24 19:30:43 CEST 2016
#52337: atk build failed in macOS Sierra 10.12
------------------------------+--------------------------------
Reporter: zhangchaowang@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Resolution: | Keywords: sierra
Port: atk |
------------------------------+--------------------------------
Comment (by ryandesign@…):
Yes #36438 sounds like what I was thinking of.
The summary is that the linker is trying to use the MacPorts copy of
libpcap, not because atk uses it, but because some system library atk uses
uses it. (And this fails because we need a universal version, which the OS
provides, but which the MacPorts copy on your system is not.) Jeremy
thought this was a linker bug, and mentioned <rdar://problem/12450551>,
but then later closed the ticket saying "There's not really anything we
can do about this. This is how the toolchain works..." The buildbot did
not encounter the problem because libpcap was not active at the time atk
was built, so the linker successfully used the universal copy of the
library provided by macOS. The build failed on our systems because we
happened to already have a non-universal copy of libpcap installed by
MacPorts. The workaround is to either deactivate libpcap for the duration
of the atk build, or else to install libpcap universal. And if you see the
same problem mentioning other ports such as dbus-python27, then the same
applies to them: either install universal, or temporarily deactivate.
Using MacPorts trace mode (`sudo port -t install ...`) may also work
around it, but you may need to build MacPorts trunk from source, as the
version of trace mode in MacPorts 2.3.x may not be sufficient for Sierra
or El Capitan.
--
Ticket URL: <https://trac.macports.org/ticket/52337#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list