[FFmpeg-cvslog] r12445 - trunk/configure

Diego Biurrun diego
Sat Mar 15 16:59:17 CET 2008


On Sat, Mar 15, 2008 at 12:31:31PM +0000, M?ns Rullg?rd wrote:
> Diego Biurrun <diego at biurrun.de> writes:
> 
> > On Sat, Mar 15, 2008 at 10:54:11AM +0100, Luca Barbato wrote:
> >> diego wrote:
> >> > 
> >> > Log:
> >> > Only check for altivec.h when not using Apple gcc and not adding -faltivec to
> >> > CFLAGS. This avoids a couple of warnings of the type
> >> > '#warning: Ignoring <altivec.h> because "-faltivec" specified'.
> >> 
> >> Recent apple gcc can use -maltivec -mabi=altivec and altivec.h
> >> I'd try to check if -maltivec is supported and then use the standard 
> >> instead of the custom stuff.
> >
> > Good idea.  I tried implementing it, but the following weirdness is
> > happening:
> >
> > Trying to run the check from configure fails:
> >
> > check_cflags -maltivec -mabi=altivec
> > check_cc -maltivec -mabi=altivec
> > BEGIN /tmp/ffmpeg-conf-12819-6389-5802.c
> >     1	int x;
> > END /tmp/ffmpeg-conf-12819-6389-5802.c
> > gcc -pipe -force_cpusubtype_ALL -Wno-sign-compare -mdynamic-no-pic -fomit-frame-pointer -maltivec -mabi=altivec -c -o /tmp/ffmpeg-conf-8187-6389-4672.o /tmp/ffmpeg-conf-12819-6389-5802.c
> > cc1: error: invalid option 'altivec -mabi=altivec'
> >
> > But running the very same gcc invocation from the command line succeeds!
> > What's going on here?
> 
> Probably some shell quoting.  Did you by any chance do
> check_cflags "-maltivec -mabi=altivec"?  If so, get rid of the quotes.

Spot on.  Fix committed.

Diego




More information about the ffmpeg-cvslog mailing list