[MacPorts] #42188: Dependency error in ffmpeg 2.1.3_1 on libogg 1.3.1_0
MacPorts
noreply at macports.org
Sat Jan 18 17:56:53 PST 2014
#42188: Dependency error in ffmpeg 2.1.3_1 on libogg 1.3.1_0
----------------------+----------------------
Reporter: me@… | Owner: devans@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.2.1
Resolution: invalid | Keywords:
Port: ffmpeg |
----------------------+----------------------
Changes (by cal@…):
* status: assigned => closed
* resolution: => invalid
Comment:
`DYLD_LIBRARY_PATH` on OS X does not behave like `LD_LIBRARY_PATH` on
Linux. Despite this fact, several tools advise setting `DYLD_LIBRARY_PATH`
on OS X in their documentation. This can lead to the problem you are
seeing at hand – setting `DYLD_LIBRARY_PATH` makes the loader prefer any
file with the same basename (in this case `libogg.0.dylib`) from the paths
listed in `DYLD_LIBRARY_PATH` to those at the URL the binary linked to
(which is what you see in the output of `otool -L /opt/local/bin/ffmpeg`).
As a consequence, just must not have `DYLD_LIBRARY_PATH` set when using
ffmpeg. As a precaution, you should only set it when you need to run
whatever software requires it. In fact, it is advisable to modify the
software requiring the variable in a way that it no longer needs it. You
may do so using `install_name_tool`, by changing the paths referenced by
its binaries and libraries to absolute ones referencing the appropriate
versions of the libraries in `/usr/local/xuggler/lib`. You may have to
adjust this for the binaries in `/usr/local/xuggler/bin`,
`/usr/local/xuggler/sbin` and `/usr/local/xuggler/lib`. If you can, please
advise upstream of xuggler (or any other location that gave you the advice
to set `DYLD_LIBRARY_PATH`) to avoid this and instead fix the paths in the
binaries.
--
Ticket URL: <https://trac.macports.org/ticket/42188#comment:5>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list