[FFmpeg-user] OSX lion, trying to compile from git fails

Boštjan Strojan bostjan.strojan at gmail.com
Mon Dec 12 20:25:16 CET 2011


got it compiled ! with:

./configure --prefix=${SOURCE} --enable-gpl --enable-libx264
--cc=clang --enable-runtime-cpudetect && make -j 4 && make install

thanks

2011/12/12 Boštjan Strojan <bostjan.strojan at gmail.com>:
> does this look right:
>
>  yasm --version
> yasm 1.2.0
> Compiled on Dec  6 2011.
> Copyright (c) 2001-2011 Peter Johnson and other Yasm developers.
> Run yasm --license for licensing overview and summary.
>
> gcc --version
> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc.
> build 5658) (LLVM build 2336.1.00)
> Copyright (C) 2007 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> ?
>
> On Sun, Dec 11, 2011 at 11:17 PM, Jim Worrall <coniophora at gmail.com> wrote:
>>
>> On Dec 11, 2011, at 2:50 PM, Carl Eugen Hoyos wrote:
>>
>>> Boštjan Strojan <bostjan.strojan <at> gmail.com> writes:
>>>
>>>> However --cc-clang says to be unsupported switch?
>>>
>>> ./configure --cc=clang
>>
>> Sorry for the error, Carl is right of course.  And if it still doesn't work you may
>> need to get the latest Xcode/Developer's Tools, especially if you haven't
>> updated that since Lion came out.
>>
>>> As said, you should not use --enable-nonfree, it does not do anything useful in
>>> your configure line.
>>> Do not use --enable-runtime-cpudetect unless you have a reason to (= if you are
>>> not a user, but a distributor. This case would be one more reason not to use
>>> --enable-nonfree)
>>>
>>> --enable-pthreads --enable-avfilter --enable-filters are default and should
>>> therefore be redundant (consider checking configure's output if pthreads are
>>> correctly detected, I could of course be wrong)
>>>
>>> And I would suggest not to use --arch at all unless there is a reason.
>>
>> I can't remember why I started using --arch=x86_64, I think one
>> of my libraries wasn't found correctly without it, but I could be wrong.
>> I'll try it without.
>>
>> _______________________________________________
>> ffmpeg-user mailing list
>> ffmpeg-user at ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
>
>
> --
> Boštjan Strojan
> +386 51 324 052 mobile


More information about the ffmpeg-user mailing list