[FFmpeg-user] what x264 version to build ffmpeg 3.4.1?

Reindl Harald h.reindl at thelounge.net
Mon Jan 15 03:36:29 EET 2018

Am 14.01.2018 um 22:47 schrieb Carl Eugen Hoyos:
> 2018-01-14 17:32 GMT+01:00 Reindl Harald <h.reindl at thelounge.net>:
>> 0.155.2893 is currently not useable for ffmpeg
> This sounds unlikely

ok, a fresh snaphot works but what do you expect when there is no 
repsonse that it should now work in the other thread i started around 
christmas and that below is the last i heard? that i try every day a new 

"config.log" is still not created at all, configure now only takes a 
long time without any output and whines in yellow color "WARNING: using 
libx264 without pkg-config"

you also did *not* confirm that you built a static x264 in a non-default 
directory and used the exact same configures as i did by try to find out 
why config.log is missing and in that context your typical "scripts are 
not supported here" is hardly helpful

frankly i even provided the exact fuile-list auf my x264-latest staic 
package and all other informations from 2017-12-25 to 2018-01-11

-------- Weitergeleitete Nachricht --------
Betreff: Re: [FFmpeg-user] x264 0.155.2893 (very recent changes)
Datum: Thu, 11 Jan 2018 13:20:30 +0100
Von: Carl Eugen Hoyos <ceffmpeg at gmail.com>
Antwort an: FFmpeg user questions <ffmpeg-user at ffmpeg.org>
An: FFmpeg user questions <ffmpeg-user at ffmpeg.org>

2018-01-11 13:05 GMT+01:00 Reindl Harald <h.reindl at thelounge.net>:
 > Am 11.01.2018 um 11:54 schrieb Carl Eugen Hoyos:

 >> You claim that there is no config.log file in your FFmpeg build
 >> directory (or its subdirectory ffbuild): How can I reproduce this?
 > by doing the same as i did?

The moment I start configure, config.log is created, no matter if
configure succeeds or not, the file config.log exists and shows
some information.
This appears unrelated to the options I pass to configure.

I also have a system where the configure scripts runs for more
than 150 minutes, on that system, I also watch config.log to
see the progress.

So while this sounds like an important issue, I have no idea
how to reproduce.

More information about the ffmpeg-user mailing list