[MacPorts] #30212: wine, wine-devel: CUPS not functioning
MacPorts
noreply at macports.org
Tue Mar 13 08:08:36 PDT 2012
#30212: wine, wine-devel: CUPS not functioning
---------------------------------+------------------------------------------
Reporter: j.s.steer@… | Owner: ryandesign@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: haspatch | Port: wine, wine-devel
---------------------------------+------------------------------------------
Comment(by chrisk@…):
I believe having an empty value for DYLD_FALLBACK_LIBRARY_PATH actually
means "$HOME/lib;/usr/local/lib;/usr/lib" somewhere inside the dlopen()
logic. At least that is what I gather from the Apple reference here:
https://developer.apple.com/library/mac/#documentation/DeveloperTools/Reference/MachOReference/Reference/reference.html#//apple_ref/c/func/dlopen
As such, having macports set its own value, seems to not just have the
positive effect of adding a new path. It also seems to have a negative
effect of causing dlopen() to ignore the standard paths. Based on that
assumption, forcing /usr/lib back in as you are doing with your new patch
makes sense and is likely the safest approach to solve this problem.
A slightly broader approach for your consideration would be to add a
little intelligence to the setting of the FALLBACK value. My thought is
to have the wrapper script tack its new path value on the tail end of
whatever FALLBACK value is already set. In cases where nothing has been
previously set, it would plug in the documented standard system defaults.
Something like this:
DYLD_FALLBACK_LIBRARY_PATH="${DYLD_FALLBACK_LIBRARY:-$HOME/lib:/usr/local/lib:/usr/lib}:@PREFIX@/lib"
Thoughts?
--
Ticket URL: <https://trac.macports.org/ticket/30212#comment:7>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list