ffmpeg 3.2.x changed compatibility version?

[RJVB (René Bertin)]

Apologies if this has already been reported/discussed:

FFMpeg 3.2.2 is supposed to be ABI-compatible with earlier versions at least down to 3.1.4, but there's a caveat (seen on 10.9.5):

Incompatible library version: /opt/local/lib/mlt/libmltavformat.dylib requires version 6.0.0 or later, but /opt/local/lib/libavfilter.6.dylib provides version 0.0.0
Incompatible library version: /opt/local/lib/mlt/libmltavformat.dylib requires version 57.0.0 or later, but /opt/local/lib/libavdevice.57.dylib provides version 0.0.0
Incompatible library version: /opt/local/lib/mlt/libmltavformat.dylib requires version 4.0.0 or later, but /opt/local/lib/libswscale.4.dylib provides version 0.0.0
Incompatible library version: /opt/local/lib/mlt/libmltavformat.dylib requires version 57.0.0 or later, but /opt/local/lib/libavformat.57.dylib provides version 0.0.0
Incompatible library version: /opt/local/lib/mlt/libmltavformat.dylib requires version 55.0.0 or later, but /opt/local/lib/libavutil.55.dylib provides version 0.0.0
Incompatible library version: /opt/local/lib/mlt/libmltavformat.dylib requires version 57.0.0 or later, but /opt/local/lib/libavcodec.57.dylib provides version 0.0.0

Not sure if that's really a "defect" but it does seem weird that the compatibility version regresses to 0.0.0 like that.

[dbevans (David B. Evans)]

I'm not sure where these messages are coming from so would help if you could provide some context (i.e. what were you doing when these messages occurred?

I'm not seeing this problem here. Using otool with the latest ffmpeg @3.2.2 and mlt @6.4.1 installed, I get the following, which seems correct:

$ otool -L /opt/local/lib/mlt/libmltavformat.dylib
/opt/local/lib/mlt/libmltavformat.dylib:
	../libmltavformat.dylib (compatibility version 0.0.0, current version 0.0.0)
	/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1504.82.0)
	/opt/local/lib/libSDL-1.2.0.dylib (compatibility version 12.0.0, current version 12.4.0)
	/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 22.0.0)
	/opt/local/lib/libmlt.6.dylib (compatibility version 6.0.0, current version 6.4.1)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.50.2)
	/opt/local/lib/libavcodec.57.dylib (compatibility version 57.0.0, current version 57.64.101)
	/opt/local/lib/libavutil.55.dylib (compatibility version 55.0.0, current version 55.34.100)
	/opt/local/lib/libavformat.57.dylib (compatibility version 57.0.0, current version 57.56.100)
	/opt/local/lib/libswscale.4.dylib (compatibility version 4.0.0, current version 4.2.100)
	/opt/local/lib/libavdevice.57.dylib (compatibility version 57.0.0, current version 57.1.100)
	/opt/local/lib/libavfilter.6.dylib (compatibility version 6.0.0, current version 6.65.100)}}}

Which versions do you have installed? if you're not using these latest versions, please update your ports tree and try again:

sudo port selfupdate
sudo port upgrade outdated

[RJVB (René Bertin)]

Replying to dbevans:

I'm not sure where these messages are coming from so would help if you could provide some context (i.e. what were you doing when these messages occurred?

Sorry, they came from port -v rev-upgrade.

I'm not seeing this problem here. Using otool with the latest ffmpeg @3.2.2 and mlt @6.4.1 installed, I get the following, which seems correct:

$ otool -L /opt/local/lib/mlt/libmltavformat.dylib

On my system, *after* rebuilding mlt (mlt-qt5 but that's irrelevant here):

> otool -L /opt/local/lib/mlt/libmltavformat.dylib
/opt/local/lib/mlt/libmltavformat.dylib:
	../libmltavformat.dylib (compatibility version 0.0.0, current version 0.0.0)
	/opt/local/lib/libmlt.6.dylib (compatibility version 6.0.0, current version 6.4.1)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)
	/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1265.21.0)
	/opt/local/lib/libSDL-1.2.0.dylib (compatibility version 12.0.0, current version 12.4.0)
	/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 20.0.0)
	/opt/local/lib/libavcodec.57.dylib (compatibility version 0.0.0, current version 57.64.101)
	/opt/local/lib/libavutil.55.dylib (compatibility version 0.0.0, current version 55.34.100)
	/opt/local/lib/libavformat.57.dylib (compatibility version 0.0.0, current version 57.56.100)
	/opt/local/lib/libswscale.4.dylib (compatibility version 0.0.0, current version 4.2.100)
	/opt/local/lib/libavdevice.57.dylib (compatibility version 0.0.0, current version 57.1.100)
	/opt/local/lib/libavfilter.6.dylib (compatibility version 0.0.0, current version 6.65.100)

Note the compatibility version of the ffmpeg libraries.

Which versions do you have installed? if you're not using these latest versions, please update your ports tree and try again:

> port installed ffmpeg mlt-qt5
The following ports are currently installed:
  ffmpeg @3.2.2_3+gpl2+gpl3+high10+libdc1394+librtmp+nonfree+x11 (active)
  mlt-qt5 @6.4.1_0+gtk2+qt5kde (active)

(A bit unnecessary to ask, no? I discovered the issue after updating ffmpeg and I was the last to update the mlt port ...)

[chrstphrchvz (Christopher Chavez)]

ffmpeg has since been updated to 4.2.3, and the libraries it installs appear to have reasonable compatibility versions set (libavfilter.7.dylib: 7.0.0, libavdevice.58.dylib: 58.0.0, libavformat.58.dylib: 58.0.0, libswscale.5.dylib: 5.0.0, libavutil.56.dylib: 56.0.0, libavcodec.58.dylib: 58.0.0).

Is this problem still relevant, or can this ticket be closed?

[RJVB (René Bertin)]

No, it can be closed.