ffmpeg build failure
Jeremy Huddleston Sequoia
jeremyhu at macports.org
Fri Jun 22 14:59:56 PDT 2012
clang: error: cannot use 'cpp-output' output with multiple -arch options
ffmpeg and ffmpeg-devel use muniversal, so there shouldn't be multiple -arch arguments. Indeed, I have ffmpeg +universal built on a couple machines just fine.
On Jun 21, 2012, at 9:42 PM, anot bot <anotbot at me.com> wrote:
> Hi Brandon / Ryan
> Here is config.log and extract that I think shows the problem... but not sure how to fix it :-)
> /opt/local/bin/clang-mp-3.0 -I/opt/local/include -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -pipe -O2 -DHAVE_LRINTF -I/opt/local/include -arch x86_64 -arch i386 -std=c99 -fomit-frame-pointer -I/opt/local/include/dirac -L/opt/local/lib -c -o /tmp/ffconf.IlmHjfLm.o /tmp/ffconf.Q1afPsbs.c
> clang: warning: argument unused during compilation: '-L/opt/local/lib'
> /opt/local/bin/clang-mp-3.0 -L/opt/local/lib -arch x86_64 -arch i386 -Wl,-dynamic,-search_paths_first -I/opt/local/include/dirac -L/opt/local/lib -o /tmp/ffconf.v109UDbe /tmp/ffconf.IlmHjfLm.o -ldirac_encoder -ldirac_decoder -lstdc++ -lbz2
> check_lib lame/lame.h lame_set_VBR_quality -lmp3lame
> check_header lame/lame.h
> BEGIN /tmp/ffconf.Q1afPsbs.c
> 1 #include <lame/lame.h>
> 2 int x;
> END /tmp/ffconf.Q1afPsbs.c
> /opt/local/bin/clang-mp-3.0 -I/opt/local/include -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -pipe -O2 -DHAVE_LRINTF -I/opt/local/include -arch x86_64 -arch i386 -std=c99 -fomit-frame-pointer -I/opt/local/include/dirac -E -o /tmp/ffconf.IlmHjfLm.o /tmp/ffconf.Q1afPsbs.c
> clang: error: cannot use 'cpp-output' output with multiple -arch options
> ERROR: libmp3lame >= 3.98.3 not found
> On 22 Jun 2012, at 05:44, Brandon Allbery wrote:
>> On Fri, Jun 22, 2012 at 12:09 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
>> On Jun 21, 2012, at 18:03, anot bot wrote:
>> > Trying to build ffmpeg +universal and getting the following error ( log file attached) :
>> ERROR: libmp3lame >= 3.98.3 not found
>> I don't know what port is supposed to provide that library.
>> The port that provides it is lame, which the log shows is already installed. I think we need to see config.log from the configure output to see why it's not detecting the library properly.
>> brandon s allbery allbery.b at gmail.com
>> wandering unix systems administrator (available) (412) 475-9364 vm/sms
> macports-users mailing list
> macports-users at lists.macosforge.org
More information about the macports-users