[MacPorts] #67173: ffmpeg-upstream @5.1.2_4+gpl2+gpl3: broken build

MacPorts noreply at macports.org
Sat Apr 1 20:30:36 UTC 2023


#67173: ffmpeg-upstream @5.1.2_4+gpl2+gpl3: broken build
------------------------------+----------------------
  Reporter:  townba           |      Owner:  mascguy
      Type:  defect           |     Status:  assigned
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.8.1
Resolution:                   |   Keywords:
      Port:  ffmpeg-upstream  |
------------------------------+----------------------

Comment (by townba):

 Attached `main.log.gz`.

 At first I thought adding `-k` was making it work, but then I saw that
 `ffmpeg` and the others are still referencing the libraries in the build
 location. Partial `otool -L /opt/local/bin/ffmpeg` output:

 {{{
 /opt/local/bin/ffmpeg:
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
 .org_macports_release_tarballs_ports_multimedia_ffmpeg-upstream/ffmpeg-
 upstream/work/destroot/opt/local/lib/libavdevice.59.dylib (compatibility
 version 59.0.0, current version 59.7.100)
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
 .org_macports_release_tarballs_ports_multimedia_ffmpeg-upstream/ffmpeg-
 upstream/work/destroot/opt/local/lib/libavfilter.8.dylib (compatibility
 version 8.0.0, current version 8.44.100)
         /opt/local/lib/libavformat.59.dylib (compatibility version 59.0.0,
 current version 59.27.100)
         /opt/local/lib/libavcodec.59.dylib (compatibility version 59.0.0,
 current version 59.37.100)
 ...
 }}}

 The binary works until I clean because `-k` kept the build location. Of
 course, once I run `sudo port clean ffmpeg-upstream`, the binary stops
 working.

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


More information about the macports-tickets mailing list