[FFmpeg-devel] MacOS X Compile error with swscale

[Diego Biurrun]

On Sat, Mar 29, 2008 at 05:48:05PM +0100, Michael Niedermayer wrote:
> On Sat, Mar 29, 2008 at 05:25:05PM +0100, Diego Biurrun wrote:
> > On Sat, Mar 29, 2008 at 04:47:54AM -0600, Scott Harper wrote:
> > > I'm using the latest svn as of this writing.
> > > 
> > > I configure ffmpeg as follows:
> > > 
> > > ./configure --enable-shared --enable-gpl --disable-mmx --enable- 
> > > libmp3lame --disable-vhook --enable-libfaad --enable-libfaac --enable- 
> > > swscale
> > > 
> > > And I get the following error:
> > > 
> > > yuv2rgb.c: In function ?yuv2rgb_get_func_ptr?:
> > > yuv2rgb.c:609: error: ?yuv420_rgb32_MMX2? undeclared (first use in  
> > > this function)
> > > yuv2rgb.c:609: error: (Each undeclared identifier is reported only once
> > > yuv2rgb.c:609: error: for each function it appears in.)
> > > yuv2rgb.c:610: error: ?yuv420_rgb24_MMX2? undeclared (first use in  
> > > this function)
> > > yuv2rgb.c:611: error: ?yuv420_rgb16_MMX2? undeclared (first use in  
> > > this function)
> > > yuv2rgb.c:612: error: ?yuv420_rgb15_MMX2? undeclared (first use in  
> > > this function)
> > > yuv2rgb.c:617: error: ?yuv420_rgb32_MMX? undeclared (first use in this  
> > > function)
> > > yuv2rgb.c:618: error: ?yuv420_rgb24_MMX? undeclared (first use in this  
> > > function)
> > > yuv2rgb.c:619: error: ?yuv420_rgb16_MMX? undeclared (first use in this  
> > > function)
> > > yuv2rgb.c:620: error: ?yuv420_rgb15_MMX? undeclared (first use in this  
> > > function)
> > > make[1]: *** [yuv2rgb.o] Error 1
> > > make: *** [lib] Error 2
> > > 
> > > Looks like it's still trying to use some MMX code, even though I  
> > > disabled it, perhaps?  (I'm open to being completely wrong about this.)
> > 
> > It is trying to use MMX2 code, not MMX code.  You could add
> > --disable-mmx2 to the command line to make compilation go through
> > or try the patch I created to fix the situation.
> 
> MMX2 implicates MMX.
> Having the defines for MMX2 set but not the ones for MMX is a bug in 
> configure IMO.

That one is fixed easily.

Diego