headers
anot bot | 22 Jun 2012 01:03

ffmpeg build failure

Hi 

Trying to build ffmpeg +universal and getting the following error  ( log file attached) :

--->  Attempting to fetch ffmpeg-0.7.11_1+mmx+universal.darwin_11.i386-x86_64.tbz2 from http://packages.macports.org/ffmpeg
--->  Fetching distfiles for ffmpeg
--->  Verifying checksum(s) for ffmpeg
--->  Extracting ffmpeg
--->  Applying patches to ffmpeg
--->  Configuring ffmpeg
Error: org.macports.configure for port ffmpeg returned: configure failure: command execution failed
Please see the log file for port ffmpeg for details:
   /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/ffmpeg/main.log
To report a bug, follow the instructions in the guide:
   http://guide.macports.org/#project.tickets
Error: Processing of port ffmpeg failed

Any help would be much appreciated :-)

cheers

anot

Hi 

Trying to build ffmpeg +universal and getting the following error  ( log file attached) :

--->  Attempting to fetch ffmpeg-0.7.11_1+mmx+universal.darwin_11.i386-x86_64.tbz2 from http://packages.macports.org/ffmpeg
--->  Fetching distfiles for ffmpeg
(Continue reading)

Permalink | Reply |
headers
Ryan Schmidt | 22 Jun 2012 06:09
Favicon

Re: ffmpeg build failure


On Jun 21, 2012, at 18:03, anot bot wrote:

> Trying to build ffmpeg +universal and getting the following error  ( log file attached) :
> 
> --->  Attempting to fetch ffmpeg-0.7.11_1+mmx+universal.darwin_11.i386-x86_64.tbz2 from http://packages.macports.org/ffmpeg
> --->  Fetching distfiles for ffmpeg
> --->  Verifying checksum(s) for ffmpeg
> --->  Extracting ffmpeg
> --->  Applying patches to ffmpeg
> --->  Configuring ffmpeg
> Error: org.macports.configure for port ffmpeg returned: configure failure: command execution failed
> Please see the log file for port ffmpeg for details:
>    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/ffmpeg/main.log
> To report a bug, follow the instructions in the guide:
>    http://guide.macports.org/#project.tickets
> Error: Processing of port ffmpeg failed
> 
> 
> <main.log>

The log you attached says:

ERROR: libmp3lame >= 3.98.3 not found

I don't know what port is supposed to provide that library.

Consider filing a bug report in our issue tracker.
(Continue reading)

Permalink | Reply |
headers
Brandon Allbery | 22 Jun 2012 06:44
Picon
Gravatar

Re: ffmpeg build failure

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

<div><div dir="ltr">On Fri, Jun 22, 2012 at 12:09 AM, Ryan Schmidt <span dir="ltr">&lt;<a href="mailto:ryandesign <at> macports.org" target="_blank">ryandesign <at> macports.org</a>&gt;</span> wrote:<div class="gmail_quote">
<blockquote class="gmail_quote">
<div class="HOEnZb"><div class="h5">
On Jun 21, 2012, at 18:03, anot bot wrote:<br>
&gt; Trying to build ffmpeg +universal and getting the following error &nbsp;( log file attached) :<br><br>
</div></div>
ERROR: libmp3lame &gt;= 3.98.3 not found<br>
I don't know what port is supposed to provide that library.<br>
</blockquote>
<div><br></div>
<div>The port that provides it is lame, which the log shows is already installed. &nbsp;I think we need to see config.log from the configure output to see why it's not detecting the library properly.</div>
</div>
<div><br></div>-- <br>brandon s allbery &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a href="mailto:allbery.b <at> gmail.com" target="_blank">allbery.b <at> gmail.com</a><br>wandering unix systems administrator (available) &nbsp; &nbsp; (412) 475-9364 vm/sms<br><br>
</div></div>
Permalink | Reply |
headers
anot bot | 22 Jun 2012 09:42

Re: ffmpeg build failure

Hi Brandon / Ryan

Here is config.log and extract that I think shows the problem... but not sure how to fix it :-)

cheers

anot

/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
check_cpp
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
> 


Hi Brandon / Ryan

Here is config.log and extract that I think shows the problem... but not sure how to fix it :-)

cheers

anot

/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
check_cpp
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
>
Permalink | Reply |
headers
Jeremy Huddleston Sequoia | 22 Jun 2012 23:59
Favicon

Re: ffmpeg build failure

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 :-)
> 
> cheers
> 
> anot
> 
> <config.log>
> 
> 
> /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
> check_cpp
> 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
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Permalink | Reply |
headers
Ryan Schmidt | 23 Jun 2012 05:52
Favicon

Re: ffmpeg build failure

On Jun 22, 2012, at 16:59, Jeremy Huddleston Sequoia wrote:

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

Did r94553 fix this?
Permalink | Reply |

Gmane