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

MacPorts noreply at macports.org
Sun Oct 6 07:47:26 UTC 2024


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

Comment (by ryandesign):

 Replying to [comment:7 kampfflunder]:
 > In case it matters:
 > {{{
 > # md5sum
 /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
 > eff07dd19a5de8edfcacee84def0c159
 /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
 > }}}

 The result you should get on macOS 11 or later is:

 {{{
 % md5sum
 /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
 md5sum:
 /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage: No
 such file or directory
 }}}

 All system libraries and frameworks should not exist on disk as of macOS
 11; they should only be present in the dyld shared cache. If
 /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage exists
 on disk on your macOS 11 or later system, try renaming it (e.g. to
 CoreImage.off) to disable it. You might check its modification date; maybe
 that provides a clue about when it got installed. (Does it coincide with
 an OS update? OS installation? OCLP update?) There might be other files on
 disk in /System/Library/Frameworks that don't match their dyld shared
 cache counterparts that shouldn't be on disk, but checking on our macOS 15
 build machine, it looks like it is normal for some framework files to
 still be there, so I don't have a definitive command for you to run to see
 if you have any other files that you should disable. But if you get a
 similar error about some other framework being of an insufficient version,
 that might give you a clue of where to look next.

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


More information about the macports-tickets mailing list