Re: [Pysparse-developers] Compiling pysparse for Windows

[Roman G. <rom...@gm...>]

Hi Daniel

On 06.04.2010 16:31, Daniel Wheeler wrote:
> Hi, I've been struggling with trying to build pysparse version 1.1 for
> python 2.6 on windows, both XP and 7. I'm using the mingw that comes
> with pythonxy. I compiled blas and lapack from the source. I had to go
> back a few versions of lapack in order for it to work with the gcc
> (gfortran) that comes with pythonxy at least that seemed to work.
> However, a whole bunch of compile flags get automatically added to the
> pysparse compile step by mingw and I have no idea what they do.
> Anyway, the long and the short is that I can build pysparse, but I
> can't import any of the compiled modules without either getting a DLL
> error (if lapack.dll and blas.dll are not in the DLL directory) or a
> memory error (if lapack.dll and blas.dll are in the DLL directory).
>    

> The weird thing is that I need both the .lib (or .a) versions as well
> as the .dll versions of lapack and blas.
>    
To my knowledge that's normal under Windows: if you link dynamically you 
need a .lib file (at compile time) and a .dll file. If you link 
statically you need only .lib files.
> I realized that I'd stashed liblapack.a and libblas.a in the
> tools/win32 of the pysparse dist for safe keeping. Anyway, I get the
> DLL error when I use those because I don't have the dll versions of
> those libraries. I need to figure out how to just include the blas and
> lapack statically using pythonxy's mingw. This wasn't a problem in
> previous releases of pythonxy. Anyway, I need to start asking
> questions on the pythonxy list.
>
> In the mean time, is it possible that someone could get a python 2.6,
> version 1.1 installer up (using a clean checkout of tags/version-1_1).
> Thanks.
>
> On Mon, Mar 1, 2010 at 1:21 PM, Roman Geus<rom...@gm...>  wrote:
>
>
>    
>> There were some modifications necessary to make the source compatible with
>> MSVC compilers - since there is no 1.1 branch, I had to work in the trunk.
>> We can look into that when the rest works.
>>      
> Just use tags. If things need to be fixed you can create a branch from
> tags/version-1_1 (to branches/version-1_1). Tags should just be place
> holders.
>    
Yes, right. But my windows build still produces wrong results in the 
superlu module.

-- Roman