[SciPy-User] Compiling SciPy almost works

Søren Gammelmark gammelmark@phys.au...
Thu Aug 5 02:28:39 CDT 2010


When trying the manual link everything works out fine. "import _csr" 
executes without any problem. I also tried using the Intel C++ compiler 
(icpc) and then everything works out fine. I guess the default 
link-libraries are different for the programs.

Should I then just append -lstdc++ to the icc-command or what would be 
the best way of solving this?


Søren

On 2010-08-05 09:11, David wrote:
> On 08/05/2010 03:27 PM, Søren Gammelmark wrote:
>    
>> I have attached the build-log. As far as I can see it chooses the Intel
>> compiler with the correct options as it should.
>>
>> Also recompiling after removing build did not change anything (I do not
>> believe it should have, since I was quite careful of doing this with
>> every attempt).
>>      
> Could you try linking the extension "manually" and add -lstdc++, i.e..
>
> icc -fPIC -fomit-frame-pointer -O2 -g -parallel -shared
> build/temp.linux-x86_64-2.6/scipy/sparse/sparsetools/csr_wrap.o
> -Lbuild/temp.linux-x86_64-2.6 -o
> build/lib.linux-x86_64-2.6/scipy/sparse/sparsetools/_csr.so -lstdc++
>
> and see it you can do python -c "import _csr" in the directory where
> _csr.so is located.
>
> If this does not work, can you get the verbose output of the link (I
> think something like icc -## or icc -v should do it - the goal is to see
> every line used by the driver icc to get the exact options used for linking)
>
> cheers,
>
> David
> _______________________________________________
> SciPy-User mailing list
> SciPy-User@scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-user
>    



More information about the SciPy-User mailing list