Opened 12 months ago

Last modified 8 months ago

#55198 assigned defect

ffmpeg @3.4: ld: cannot link directly with /System/Library/Frameworks//CoreImage.framework/CoreImage

Reported by: fhgwright (Fred Wright) Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version:
Keywords: mavericks Cc: jeremyhu (Jeremy Huddleston Sequoia)
Port: ffmpeg

Description

The ostensible error is:

ERROR: gnutls not found using pkg-config

But that appears to be bogus:

MacPro:~ fw$ pkg-config --libs gnutls
-L/opt/local/lib -lgnutls

The real error may be:

ld: cannot link directly with /System/Library/Frameworks//CoreImage.framework/CoreImage.  Link against the umbrella framework 'QuartzCore.framework' instead. for architecture x86_64

Attaching both main.log and config.log

Attachments (4)

main.log (49.3 KB) - added by fhgwright (Fred Wright) 12 months ago.
config.log (517.7 KB) - added by fhgwright (Fred Wright) 12 months ago.
ffmpeg.build.log (3.2 MB) - added by kencu (Ken) 8 months ago.
10.9 successful build
ffmpeg.config.log (804.4 KB) - added by kencu (Ken) 8 months ago.
10.9 successful config

Change History (12)

Changed 12 months ago by fhgwright (Fred Wright)

Attachment: main.log added

Changed 12 months ago by fhgwright (Fred Wright)

Attachment: config.log added

comment:1 Changed 12 months ago by ryandesign (Ryan Schmidt)

Cc: dbevans removed
Keywords: mavericks added
Owner: set to dbevans
Status: newassigned
Summary: ffmpeg configure fails on 10.9.5ffmpeg @3.4: ld: cannot link directly with /System/Library/Frameworks//CoreImage.framework/CoreImage

comment:2 Changed 11 months ago by fhgwright (Fred Wright)

Although I originally encountered this on 10.9.5, the lack of binary packages more recent than 3.3.4 on any OSX version suggests that the 3.4 update is completely broken.

comment:3 Changed 11 months ago by kencu (Ken)

I didn't have any trouble on 10.6.8 with either ffmpeg or ffmpeg-devel:

$ sudo port -v installed | grep ffmpeg
  ffmpeg @3.4_0+gpl2 (active) platform='darwin 10' archs='x86_64' date='2017-11-08T21:10:38-0800'
  ffmpeg-devel @20171018_0+gpl2+gpl3+nonfree platform='darwin 10' archs='x86_64' date='2017-10-21T16:13:57-0700'

it also installed on 10.5 Leopard PPC, FWIW:

$ port -v installed ffmpeg
The following ports are currently installed:
  ffmpeg @3.4_0+gpl2+gpl3+nonfree (active) platform='darwin 9' archs='ppc' date='2017-10-20T18:46:03-0700'

comment:4 in reply to:  2 ; Changed 8 months ago by ryandesign (Ryan Schmidt)

Replying to fhgwright:

Although I originally encountered this on 10.9.5, the lack of binary packages more recent than 3.3.4 on any OSX version suggests that the 3.4 update is completely broken.

No, it only suggests that ffmpeg is not distributable.

comment:5 in reply to:  4 Changed 8 months ago by fhgwright (Fred Wright)

Replying to ryandesign:

Replying to fhgwright:

Although I originally encountered this on 10.9.5, the lack of binary packages more recent than 3.3.4 on any OSX version suggests that the 3.4 update is completely broken.

No, it only suggests that ffmpeg is not distributable.

Perhaps, but how would it change from distributable to not distributable with no change to the license field in the Portfile? This is *not* the 'nonfree' variant.

In any case, it remains broken (at least on two machines running 10.9.5) after four months.

comment:6 Changed 8 months ago by jmroot (Joshua Root)

% ./port_binary_distributable.tcl -v ffmpeg
"ffmpeg" is not distributable because its license "gpl" conflicts with license "EPL-1" of dependency "graphviz"

comment:7 Changed 8 months ago by kencu (Ken)

I booted up my 10.9.5 VM to see what was up, and ffmpeg built right on through with the default options:

$ port -v installed ffmpeg
The following ports are currently installed:
  ffmpeg @3.4.2_0+gpl2 (active) platform='darwin 13' archs='x86_64' date='2018-02-28T23:02:58-0800'

So no doubt you will find that frustrating. I'll post up my build log and config log for you to look at.

look carefully at /usr/local to see if there is anything in there that is confusing your installation. You might consider deleting or moving /usr/local to be sure it's out of the way.

Another place that things get stuck is /Library/Frameworks and you might look in there for anything conflicting.

Changed 8 months ago by kencu (Ken)

Attachment: ffmpeg.build.log added

10.9 successful build

Changed 8 months ago by kencu (Ken)

Attachment: ffmpeg.config.log added

10.9 successful config

comment:8 Changed 8 months ago by kencu (Ken)

For reasons that are not completely clear to me, our configure lines do not match up:

# ./configure --prefix=/opt/local --enable-swscale --enable-avfilter --enable-avresample --enable-libmp3lame --enable-libvorbis --enable-libopus --enable-librsvg --enable-libtheora --enable-libopenjpeg --enable-libmodplug --enable-libvpx --enable-libsoxr --enable-libspeex --enable-libass --enable-libbluray --enable-lzma --enable-gnutls --enable-fontconfig --enable-libfreetype --enable-libfribidi --disable-jack --disable-libopencore-amrnb --disable-libopencore-amrwb --disable-libxcb --disable-libxcb-shm --disable-libxcb-xfixes --disable-indev=jack --enable-opencl --disable-outdev=xv --enable-audiotoolbox --enable-videotoolbox --enable-sdl2 --mandir=/opt/local/share/man --enable-shared --enable-pthreads --cc=/usr/bin/clang --arch=x86_64 --enable-x86asm --enable-libx265 --enable-gpl --enable-postproc --enable-libx264 --enable-libxvid
# ./configure --prefix=/opt/local --enable-swscale --enable-avfilter --enable-avresample --enable-libmp3lame --enable-libvorbis --enable-libopus --enable-librsvg --enable-libtheora --enable-libopenjpeg --enable-libmodplug --enable-libvpx --enable-libsoxr --enable-libspeex --enable-libass --enable-libbluray --enable-lzma --enable-gnutls --enable-fontconfig --enable-libfreetype --enable-libfribidi --disable-indev=jack --disable-outdev=xv --enable-audiotoolbox --enable-sdl2 --mandir=/opt/local/share/man --enable-shared --enable-pthreads --cc=/usr/bin/clang --enable-videotoolbox --enable-libx265 --enable-gpl --enable-postproc --enable-libx264 --enable-libxvid --arch=x86_64 --enable-x86asm

Oh, duh -- I'm building 3.4.2, and you built 3.4.0. So that's likely why they don't match.

Last edited 8 months ago by kencu (Ken) (previous) (diff)
Note: See TracTickets for help on using tickets.