ryandesign at macports.org
Sat Mar 24 14:45:29 PDT 2007
On Mar 24, 2007, at 06:28, Takeshi Enomoto wrote:
> I'd be happy to hear from those have knowledge to suggest a fix.
> fftw-3-sigle does not build on my MacBook Pro.
> I should fix this because I am the maintainer of fftw-3 and I need
> this for GDL.
> But the error below is beyond my ability.
> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I. -I.. -I../simd -O3 -fomit-
> frame-pointer -malign-double -fstrict-aliasing -ffast-math -
> march=pentiumpro -D_THREAD_SAFE -MT trig.lo -MD -MP -MF .deps/
> trig.Tpo -c trig.c -o trig.o
> /var/tmp//ccMMtwDn.s:99:operands given don't match any known 386
> /var/tmp//ccMMtwDn.s:100:operands given don't match any known 386
> /var/tmp//ccMMtwDn.s:132:operands given don't match any known 386
> /var/tmp//ccMMtwDn.s:134:operands given don't match any known 386
> /var/tmp//ccMMtwDn.s:167:operands given don't match any known 386
> /var/tmp//ccMMtwDn.s:168:operands given don't match any known 386
> make: *** [trig.lo] Error 1
> make: *** [all-recursive] Error 1
> make: *** [all] Error 2
It sounds like it's trying to use PowerPC code when building on your
Intel Mac? Which it shouldn't do.
Someone else seems to have had this problem:
In that message he says he got it to work, though he doesn't tell us
exactly what he changed to make it work. Maybe he added -march=i386
or some such to his configure line. That seems to be the only
What is the difference between fftw-3 and fftw-3-single? Looking at
the portfiles, I'm confused. They both download the same version of
the same source archive. They have the same default configure.args.
fftw-3-single enables altivec instructions when building on PPC;
fftw-3 does not. fftw-3-single deletes some things in post-destroot;
fftw-3 does not. And fftw-3-single depends on fftw-3. This all seems
More information about the macports-dev