#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:11 cal@…]:
It's actually not ffmpeg misreporting this, but dyld, the dynamic loader on OS X. I'm not sure for what reasons it reports the incorrect path, but I suppose it just prints the path referenced from the executed binary (that is, ffmpeg in this case). The same applies to the naming of the variables. Since MacPorts is not in control of the loader, this is not our bug to fix, but Apple's, if any.
It isn't a bug. It is *correctly* reporting the dylib id of the link being resolved. That is often the path name but not always. This is clear when you have a link that is using a relative path rather than an absolute on. For example: {{{ Dyld Error Message: Library not loaded: @rpath/My.framework/Versions/A/My Referenced from: /Applications/My.app/Contents/MacOS/My Reason: image not found }}} -- Ticket URL: <https://trac.macports.org/ticket/42188#comment:12> MacPorts <http://www.macports.org/> Ports system for OS X