How did you install your compiler?  What do you get from `gcc-4.0 -v` and `which gcc-4.0` (and `which gcc`)?

It's possible that a workaround is to explicitly clear ARCHFLAGS:

    $> export ARCHFLAGS=""

-MinRK

On Fri, May 25, 2012 at 10:32 AM, Robert Bradshaw <robertwb <at> gmail.com> wrote:

On Fri, May 25, 2012 at 9:35 AM, Chris Barker <chris.barker <at> noaa.gov> wrote:
> On Thu, May 24, 2012 at 10:37 AM, Bvaidya <coolastro <at> gmail.com> wrote:
>
>> I am having this problem of compilation of a .pyx file.
>> This error is to do with an unrecognized option for the gcc compiler.
>>
>> I create a .pyx file and then setup.py as directed in the Cython 0.16 wiki.
>> Then I run the command -
>>
>> python setup.py build_ext -i
>>
>> With this I get the error >
>
>> gcc-4.0 -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -isysroot
>> /Developer/SDKs/MacOSX10.5.sdk -DNDEBUG -g -O3 -arch x86_64 -isysroot
>> /Developer/SDKs/MacOSX10.5.sdk
>> -I/Library/Frameworks/EPD64.framework/Versions/7.2/lib/python2.7/site-packages/numpy/core/include
>
> I take it this is the EPD distribution -- this may be a question for
> the EPD folks -- I wonder if they do anything odd with the compiler?
> (though I wouldn't think so) -- and Cython is certainly a common use
> case for EPD users (though this doesn't look like Cython issue --
> you'd have the same issue compiling any extension with distutils.

This is a distutils/c compiler issue, not Cython (in fact Cython is
skipped "skipping 'laplace.c' Cython extension (up-to-date)"). It
looks like you downloaded a binary not compiled with the same compiler
that you have. You could try re-compiling Python from source to get
rid of this problem for sure; otherwise contact the people you got the
binary from for help.

- Robert