#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@…): Replying to [comment:15 me@…]:
Replying to [comment:14 larryv@…]:
Replying to [comment:13 me@…]:
IME Apple bug reports are useless, so I won't bother.
That’s fine, because there is no Apple bug here.
Apple's dyld is giving a misleading error message (failing to distinguish the dylib id - the same string as a file path - from an actual file path), which is a bug.
Yes, I actually filed an enhancement request yesterday to provide this extra information in dlerror(), but as Larry mentioned, you can use DYLD_PRINT_LIBRARIES to debug issues like this. The "Library not loaded:" line is correct. The fact that you are confusing the dylib id and the path of the file actually loaded is unfortunate but not really a bug. The behavior is not a bug.
And when it does so, it could warn you that your configuration is broken so ports it installs can't be expected to work. When it scans for linking errors it could check against DYLD_LIBRARY_PATH, predict what the misleading error messages will be, and clarify them individually.
This isn't a linking error. It's an issue at load time. ffmpeg linked successfully. Replying to [comment:16 larryv@…]:
In any case, this is irrelevant because most of us don’t work at Apple and can’t change `dyld`.
Note that dyld is OSS, and if you really care about fixing this error message, I'll pass along a patch for you. Otherwise, you'll have to wait until Nick (or I) get some cycles to make the change. -- Ticket URL: <https://trac.macports.org/ticket/42188#comment:17> MacPorts <http://www.macports.org/> Ports system for OS X