[MacPorts] #70882: OpenCore Legacy Patcher 2.0.2 installs faulty CoreImage framework on macOS 15 on Macs using 3802-based GPUs

[MacPorts]

#70882: OpenCore Legacy Patcher 2.0.2 installs faulty CoreImage framework on macOS
15 on Macs using 3802-based GPUs
-------------------------------------------------+-------------------------
  Reporter:  RivetBenoit                         |      Owner:  (none)
      Type:  defect                              |     Status:  assigned
  Priority:  Normal                              |  Milestone:
 Component:  ports                               |    Version:  2.10.1
Resolution:                                      |   Keywords:  sequoia
      Port:  ffmpeg, ffmpeg6, ffmpeg7, ffmpeg-   |
  devel                                          |
-------------------------------------------------+-------------------------

Comment (by ryandesign):

 Replying to [comment:33 kampfflunder]:
 > Ah, I noticed that the +nonfree crashes:

 > While the "regular" variant is fine:

 Probably nothing to do with variants. The "regular" set of variants are
 built by our buildbot infrastructure, so you probably received a binary.
 If our binary worked, what gets installed on your system should work.

 However, when you specify non-default variants like +nonfree, you must
 build from source on your system.


 > While `+nonfree` crashes:
 > {{{
 > ❯ ffmpeg
 > dyld[28367]: Library not loaded: /opt/local/lib/libavcodec.58.dylib
 >   Referenced from: <8FAB48B7-BAF9-32FA-88C8-7D23395C3792>
 /opt/local/bin/ffmpeg
 >   Reason: tried: '/opt/local/lib/libavcodec.58.dylib' (not a mach-o
 file),
 '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libavcodec.58.dylib'
 (no such file), '/opt/local/lib/libavcodec.58.dylib' (not a mach-o file),
 '/opt/local/lib/libavcodec.58.134.100.dylib' (not a mach-o file),
 '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libavcodec.58.134.100.dylib'
 (no such file), '/opt/local/lib/libavcodec.58.134.100.dylib' (not a mach-o
 file)
 > [1]    28367 abort      ffmpeg
 > }}}
 > But this seems to be another problem?

 This sounds like the APFS cache bug with files that have (or had) holes;
 see #67336. It happens seemingly at random so if you simply rebuild the
 port again (`sudo port -ns upgrade --force ffmpeg`) it might not hit you
 this time. It [https://lists.macports.org/pipermail/macports-
 users/2024-October/053091.html did affect the macOS 15 x86_64 ffmpeg
 binary] our server produced a few weeks ago, and then on subsequent
 rebuilds the problem went away. Josh has committed a workaround for this
 problem to the latest not-yet-released macports-base so you could also
 build the latest macports-base from source.

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