[MEncoder-users] mencoder -> x264 ? (mencoder: to exclusive)

[Sebastian]

Bob: Uhm just wanted to chime in here and mention that I had a similar
problem when trying to compile mplayer/mencoder a week ago (configure
not detecting x264). Gave up later and went with the binary package of
my distribution. So this may be not entirely your fault?!

I'm using Arch Linux btw.

On Tue, Jun 22, 2010 at 2:40 PM, Bob Tennent <rdtennent at gmail.com> wrote:
>>> I added --enable-x264 to the configure. The compilations went well
> but the
>>> linking fails:
>>
>> You should only use --enable-x264 when absolutely needed and you're
>> sure you meet all the requirements. Recommended is to not explicitly
>> use args in configure and let the configure detect stuff by itself. If
>> it can't, it can mean four things
>>
>> 1. there's a bug in configure
>> 2. your system is missing something thus it skips it
>> 3. you have it, but it's too old so configure skips it
>> 4. configure can't detect it as it's in a non-standard path (rarely
> happens)
>
> config.log says
>
> #if X264_BUILD < 98
> #error We do not support old versions of x264. Get the latest from git.
> #endif
>
> and I believe I have 92, which is the most recent packaged version
> available for my system.
>
>  > which gcc version are you using? gcc 4.4.0 and 4.4.1 are known to
>  > miscompile mplayer (and I think x264 too). Also make sure you install
>  > a supported yasm/nasm package
>
> Why would these affect the configuration script?
>
> gcc-4.4.3-4.fc12.i686
> yasm-0.7.2-3.fc12.i686
> nasm-2.07-3.fc12.i686
>
>>> Are more recent versions needed?
>>
>> Yes, probably the latest from x264 git
>
> I'm just going to revert to the previous version until the packager
> catches up. I've reported the problem. Thanks for your help.
>
> Bob T.
>
> _______________________________________________
> MEncoder-users mailing list
> MEncoder-users at mplayerhq.hu
> https://lists.mplayerhq.hu/mailman/listinfo/mencoder-users
>
>