[MacPorts] #70882: Linking errors after installing ffmpeg, ffmpeg7

[MacPorts]

#70882: Linking errors after installing ffmpeg, ffmpeg7
------------------------------+----------------------
  Reporter:  RivetBenoit      |      Owner:  mascguy
      Type:  defect           |     Status:  assigned
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.10.1
Resolution:                   |   Keywords:  sequoia
      Port:  ffmpeg, ffmpeg7  |
------------------------------+----------------------
Changes (by ryandesign):

 * cc: kampfflunder (added)


Comment:

 Replying to [comment:3 ryandesign]:
 > The machine doing our buildbot builds for x86_64 macOS 13, 14, and 15 is
 a 2016 MacBook Pro running OpenCore Legacy Patcher.

 macOS 15 x86_64 builds are now being done on a 2018 Mac mini with no need
 for OCLP. I deleted our ffmpeg binary and had this machine recreate it
 yesterday for [ticket:67336 an unrelated reason]. The newly built ffmpeg
 still links with CoreImage compatibility version 1.0.1, current version
 6.0.0.

 I have a 2011 MacBook Pro with macOS 15.0 installed with OCLP and on that
 system ffmpeg installed from yesterday's binary works fine.

 Replying to [comment:4 kampfflunder]:
 > Same problem here.
 > Imac 27" late 2014 (Imac 15,1), MacOS Sequoia 15.0.1, OCLP 2.0.2

 Please confirm: if you run `sudo port -d rev-upgrade`, it says
 `/System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
 provides version 1.0.0`? What happens if you run `dyld_info -load_commands
 /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage | grep
 -B1 -A5 LC_ID_DYLIB`? On my system it says:

 {{{
 Load command #4
              cmd: LC_ID_DYLIB
          cmdsize: 0x60
             name:
 "/System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage"
         cur-vers: 6.0
      compat-vers: 1.0.1
 Load command #5
 }}}

 What does yours say for `cur-vers` and does your say `compat-vers: 1.0.0`
 instead? If so, I don't know how that could work; you need compatibility
 version 1.0.1 for compatibility with all existing software that uses
 CoreImage. You may need to write to an OpenCore Legacy Patcher support
 forum to see if anyone knows why this has happened and how to fix it. The
 only fix I can think of is reinstalling macOS.

-- 
Ticket URL: <https://trac.macports.org/ticket/70882#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS