[MPlayer-users] Linker error with current git version of ffmpeg in mplayer

[George R Goffe]

Hi,

I was testing an up to date (against development source) newly built gcc (experimental) version by compiling mplayer and the link step failed (see below). I tried the "out of the box" Fedora 30 x86_64 (rawhide) version of gcc (gcc-8.2.1-3.fc30.x86_64) and the link failed as well.


Has anyone seen this problem? Am I doing something wrong perhaps? Could it be mplayer?

I have a full build log if that's needed.


Best regards and thanks,

George...

/usr/bin/ld: ffmpeg/libavcodec/av1_parser.o: in function `av1_parser_parse':
av1_parser.c:(.text+0x108): undefined reference to `ff_cbs_read'
/usr/bin/ld: av1_parser.c:(.text+0x2da): undefined reference to `ff_cbs_fragment_uninit'
/usr/bin/ld: av1_parser.c:(.text+0x375): undefined reference to `ff_cbs_read'
/usr/bin/ld: av1_parser.c:(.text+0x38e): undefined reference to `ff_cbs_fragment_uninit'
/usr/bin/ld: ffmpeg/libavcodec/av1_parser.o: in function `av1_parser_close':
av1_parser.c:(.text+0x94): undefined reference to `ff_cbs_close'
/usr/bin/ld: ffmpeg/libavcodec/av1_parser.o: in function `av1_parser_init':
av1_parser.c:(.text.unlikely+0xf): undefined reference to `ff_cbs_init'
collect2: error: ld returned 1 exit status
make: *** [Makefile:747: mplayer] Error 1

[The Wanderer]

Post by George R Goffe
Hi,
I was testing an up to date (against development source) newly built
gcc (experimental) version by compiling mplayer and the link step
failed (see below). I tried the "out of the box" Fedora 30 x86_64
(rawhide) version of gcc (gcc-8.2.1-3.fc30.x86_64) and the link
failed as well.
Has anyone seen this problem? Am I doing something wrong perhaps? Could it be mplayer?

Sylvain Bertrand posted a "fix build with recent ffmpeg" patch on
mplayer-dev-eng, just yesterday. This is almost certainly the issue
which that patch is intended to fix.

It can take anywhere from a few hours to several days before someone
with commit access applies the patch, but in the meantime, it shouldn't
be hard to apply it locally yourself. (Although I do recommend applying
it against a copy of the source tree, rather than taking the risk of
forgetting to unapply it before updating after the patch gets applied
upstream.)