[MacPorts] #52337: atk build failed in macOS Sierra 10.12
MacPorts
noreply at macports.org
Mon Sep 26 11:10:57 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@…):
Replying to [comment:14 zhangchaowang@…]:
> 2. Next time please please please add some message to tell what need to
be done if depreciated any packages. To any end users, printing the error
without any further hints what need to do next is not quite helpful.
What would you have the llvm-3.5 port print? It doesn't know why you have
asked to install it, only that you have asked to install it, and it knows
that it is not compatible with your OS, so that's what it prints.
Replying to [comment:16 jeremyhu@…]:
> Something that atk links against is linking against libpcap.dylib and
the linker is resolving that to the MacPorts-provided one instead of the
system-provided one.
>
> Notice that /usr/lib/libnetwork.dylib links against libpcap.dylib, so
maybe something is linking against libnetwork.dylib.
I notice that /usr/lib/libnetwork.dylib links against
/usr/lib/libpcap.A.dylib. Why isn't it considered a bug that the linker
has decided to ignore that full path and go looking for it in the MacPorts
directory instead? What's the point of using absolute paths for
install_names if the linker ignores them?
--
Ticket URL: <https://trac.macports.org/ticket/52337#comment:17>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list