Re: [Pysparse-users] Pysparse installation problems

[Dominique O. <dom...@gm...>]

On Thu, Apr 8, 2010 at 9:50 AM, Rob Speer <rs...@mi...> wrote:
> On Wed, Apr 7, 2010 at 3:00 AM, Dominique Orban
> <dom...@gm...> wrote:
>> On Tue, Apr 6, 2010 at 12:23 AM, Rob Speer <rs...@mi...> wrote:
>>> It seems that it has something to do with the symbol hackery that
>>> defines SPMATRIX_UNIQUE_SYMBOL in a whole bunch of different places.
>>> Apparently numpy.distutils isn't handling this the way you expect.
>>>
>>> If I define NO_IMPORT_SPMATRIX, it compiles.
>>
>> This is odd. It compiles without problems for me on Mac Intel but
>> again I notice that my gcc flags are quite different from yours:
>>
>> C compiler: gcc -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall
>> -Wstrict-prototypes
>>
>> Are you using the default /usr/bin/gcc?
>
> The one that comes from Xcode, yes.
>
> The -fno-strict-aliasing option sounds relevant. Where are these
> options set, anyway?

You can set compiler options by setting the CFLAGS variable, e.g. :

% CFLAGS='-O0' python setup.py build

See http://docs.python.org/install/#building-extensions-tips-and-tricks

I'm using the gcc from http://hpc.sf.net which seems to be setting
those options automatically.

-- 
Dominique