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

Reindl Harald h.reindl at thelounge.net
Fri Aug 1 15:51:54 CEST 2014


Am 01.08.2014 um 15:35 schrieb Carl Eugen Hoyos:
> 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

anyways - any distribution packages are configured that way
it don't harm to define even defaults

>>  --incdir=%{_prefix}/local/include/ffmpeg \
> 
> Really? Doesn't this break compilation of 
> any other software that uses FFmpeg?

the goal is a *static build*

>>  --libdir=%{_prefix}/local/lib64 \
> 
>>  --shlibdir=%{_prefix}/local/lib64 \
> 
> (This may be unnecessary, but I may also 
> misremember.)

maybe, i was lucky to get ffmepg static with static x264 working after
playing around days and weeks

>>  --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.

but it don't harm

>>  --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 
> them.

why should i remove O3?

>>  --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?

what are you talking about?

i enable them explicitly!
-Wl,-z,now -Wl,-z,relro,-z,noexecstack results in a Full RELRO build
sadly PIE don't work for the static build

/usr/local/bin/ffmpeg:
 Position Independent Executable: no, normal executable!
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: yes

http://tk-blog.blogspot.co.at/2009/02/relro-not-so-well-known-memory.html
ffmpeg is especially mentioned there







-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <https://ffmpeg.org/pipermail/ffmpeg-user/attachments/20140801/21578463/attachment.asc>


More information about the ffmpeg-user mailing list