[FFmpeg-user] How to resolve “ERROR: libx264 not found”?

Carl Eugen Hoyos cehoyos at ag.or.at
Fri Aug 1 15:35:31 CEST 2014

Reindl Harald <h.reindl <at> thelounge.net> writes:

> ./configure \
>  --prefix=%{_prefix}/local \

>  --bindir=%{_prefix}/local/bin \
>  --datadir=%{_prefix}/local/share/ffmpeg \

These seem to be the default

>  --incdir=%{_prefix}/local/include/ffmpeg \

Really? Doesn't this break compilation of 
any other software that uses FFmpeg?

>  --libdir=%{_prefix}/local/lib64 \

>  --shlibdir=%{_prefix}/local/lib64 \

(This may be unnecessary, but I may also 

>  --mandir=%{_prefix}/local/man \

>  --arch=x86_64 \

I believe you misunderstand this option: It 
does not tell FFmpeg to build for x86_64, it 
tells it that your (cross-)compiler is for 
x86_64 (in case it cannot detect this which 
hopefully isn't the case). Please remove it.

>  --cpu=corei7 \

>  --extra-cflags="-I%{_prefix}/local/x264 

> -O3 -fomit-frame-pointer 
> -fno-strict-aliasing" \

There are (imo exactly) two possibilities:
Either these are necessary and useful, 
then please send a patch so that they are 
added by our configure script (or at least 
open a ticket or request a change on this 
mailing list).
Or they are not useful (or - more likely 
- make no difference), then please remove 

>  --extra-ldflags="-I%{_prefix}/local/x264 
> -L%{_prefix}/local/x264 -ldl -Wl,-z,now

> -Wl,-z,relro,-z,noexecstack" \

This always surprises me:
Do you know of an issue (in the past!) that 
was fixed by this option? Because there are 
configure switches that are known to have 
fixed security issues in the past, so why 
don't you use them?
(Assuming this is for security reasons.)

Carl Eugen

More information about the ffmpeg-user mailing list