Date: Sun, 5 Jul 2015 00:14:54 +0300 From: Raivo Hool <raivo.hool@gmail.com> To: ports@FreeBSD.org Subject: building multimedia/ffmpeg results in tons of 'undefined references' Message-ID: <BDE60DA3-8A42-46FD-933A-11D67642DCD3@gmail.com>
next in thread | raw e-mail | index | archive | help
FreeBSD 10.1-STABLE from mid-June on a Core2Duo. Building multimedia/ffmpeg invariably fails for me like this: MAN doc/ffprobe.1 MAN doc/ffmpeg-all.1 MAN doc/ffprobe-all.1 MAN doc/ffmpeg-utils.1 libavcodec/libavcodec.so: undefined reference to `ff_dcadsp_init_x86' libavcodec/libavcodec.so: undefined reference to `ff_ttadsp_init_x86' libavcodec/libavcodec.so: undefined reference to `ff_dwt_init_x86' libavcodec/libavcodec.so: undefined reference to `ff_bswapdsp_init_x86' libavcodec/libavcodec.so: undefined reference to `ff_h264dsp_init_x86' libavcodec/libavcodec.so: undefined reference to `ff_h263dsp_init_x86=E2=80= =99 Etc. Needless to say, the functions are nicely present within the files. Curiously enough, it is always multimedia/ffmpeg and never any of the = suffixed ffmpeg ports, such as multimedia/ffmpeg26, which did not used = to build when it was still called multimedia/ffmpeg, but now, having = gained the suffix, builds without an issue. There is no difference = whether I have a make.conf or not. No suffix - build fail. Suffix - no = problemo. Where should I look? I am completely at a loss. I have read through all = the man pages I could think of (ldconfig and ld, to be precise), = wandered in places the former recommended, and found nothing. The same = port builds fine on another FreeBSD machine that I administer. --=20 Raivo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BDE60DA3-8A42-46FD-933A-11D67642DCD3>