[MacPorts] #42188: Dependency error in ffmpeg 2.1.3_1 on libogg 1.3.1_0

[MacPorts]

#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   |
----------------------+----------------------

Comment (by jeremyhu@…):

 > I'm not sure this should be closed yet; ffmpeg is still misreporting the
 error, saying it's loading a different file than it's actually loading,
 and not using the fallback.

 It's not reporting the *FILE* it's reporting the *DYLIB ID*.  I understand
 your confusion, but it is correct.

 > Do you have a link describing the behavior of DYLD_LIBRARY_PATH

 Read the dyld man page.

 > From what you say it sounds like the "right way" is to never define it
 at all.

 YES!  No user should ever define it.  No released software should rely on
 it being set.  If you *REALLY* need something like it, use
 DYLD_FALLBACK_LIBRARY_PATH

 > Does install_name_tool work for all executables or just for macports
 executables?

 Anything mach-o

 >Unsetting DYLD_LIBRARY_PATH and DYLD_OVERRIDE_LIBRARY_PATH does resolve
 the error.

 As expected

 >  I didn't set them by hand based on some advice, it was done
 automatically either by the Tracker installer or an installer for a
 dependency.

 Yes, likely xuggler. (http://www.xuggle.com ?).  Go yell at them.

 > If the variable acts as an override, why isn't it
 DYLD_OVERRIDE_LIBRARY_PATH?

 It isn't an override.  It does what it's documented to do.

-- 
Ticket URL: <https://trac.macports.org/ticket/42188#comment:8>
MacPorts <http://www.macports.org/>
Ports system for OS X