Excellent, Thomas.

 

Thanks for that. Since I am not using Windows myself for this sort of thing, I’ll leave it to the community to decide what the setup.py file (and compile.py) should ultimately look like in case of the win32 architecture.

I continue to be happy to incorporate updates as you make them available, but I’d like the opinion from the rest of you before I do so.

 

Thanks again

Ole Nielsen

 

-----Original Message-----
From: Thomas.Poulet@csiro.au [mailto:Thomas.Poulet@csiro.au]
Sent: Friday, 8 May 2009 3:07 PM
To: Nielsen Ole
Cc: pypar-developers@lists.sourceforge.net
Subject: RE: question about installing pypar [SEC=UNCLASSIFIED]

 

Hi Ole,

 

Thanks for that. I finally managed to get it all working OK on Windows with Visual Studio 2003 and MPICH2.

For info, here’s what I had to do

 

I changed setup.py line 112 to replace

output = "gcc -L$MPICH_DIR\SDK.gcc\lib -lmpich -I$MPICH_DIR\SDK.gcc\include"

with

output = "gcc -L$MPICH_DIR\lib -lmpi -I$MPICH_DIR\include"

since using MPICH2 and not MPICH.

 

Then in compile.py line 112 (as well!?!) I changed the definition of python_include:

            python_include = os.path.join(sys.exec_prefix, 'include')

 

Then when running setup.py the compile and link commands printed were slightly wrong. I then ran them manually with those corrections:

 

"C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.exe" /c /nologo /Ox /MD /W3 /GX /DNDEBUG /I%MPICH_DIR%\include /IC:\Python25\lib\site-packages\numpy\core\include /IC:\Python25\include /IC:\Python25\PC /Tcmpiext.c /Fobuild\temp.win32-2.5\Release\mpiext.obj

 

"C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\link.exe" /DLL /nologo /INCREMENTAL:NO /LIBPATH:%MPICH_DIR%\lib /LIBPATH:C:\Python25\libs /LIBPATH:C:\Python25\PCBuild mpi.lib /EXPORT:initmpiext build\temp.win32-2.5\Release\mpiext.obj /OUT:build\lib.win32-2.5\pypar\mpiext.pyd /IMPLIB:build\temp.win32-2.5\Release\mpiext.lib

 

After that, setup.py ran fine with the “build” and “install” targets, and I could run a demo example OK.

Thanks,

 

Thomas.

 


From: Ole.Nielsen@ga.gov.au [mailto:Ole.Nielsen@ga.gov.au]
Sent: Thursday, 7 May 2009 10:21 AM
To: Poulet, Thomas (E&M, Kensington)
Cc: pypar-developers@lists.sourceforge.net
Subject: RE: question about installing pypar [SEC=UNCLASSIFIED]

 

Hi Thomas

 

From what you are saying the problem lies with your MPI system.

The first thing to do is to test a simple C or Fortran based MPI program such as network_timing.c or other examples like that.

If that can’t run, there is no point in trying pypar.

 

Perhaps you could try OpenMPI which seems to be the most developed MPI implementation at present.

 

I have CC’d this to the pypar mailing list so that others can chime in.

 

Cheers

Ole

 

-----Original Message-----
From: Thomas.Poulet@csiro.au [mailto:Thomas.Poulet@csiro.au]
Sent: Wednesday, 6 May 2009 7:31 PM
To: Nielsen Ole
Subject: question about installing pypar

 

Dear Oli,

 

I’m trying to install pypar on a windows machine with MPICH and visual studio 2003. I’m not having much luck though

mpirun -np 2 demo.py consistently returns

 

 

"C:\projects\pypar_2.1.0_66\demos>mpirun -np 2 demo.py

Unable to launch 'C:\projects\pypar_2.1.0_66\demos\demo.py', error 8: CreateProcess failed: Not enough storage is available to process this command."

 

This appears to have something to do with the thread stack size, but I’m not really sure.

 

I fell back to trying to compile network_timings.c (to try to test the mpich instalation) with the commands

 

cl network_timing.c /MD "/Ic:/program files/mpich/SDK/include" /Foa.obj

link a.obj "/LIBPATH:c:/program files/mpich/SDK/lib" mpich.lib

 

but this just results in the error message

 

C:\Documents and Settings\pou036\Desktop\shared>mpirun -localonly -np 2 a.exe

Wait for process 0 to write port to temporary file timed out

 

I was just wondering if you had any suggestions…

Cheers,

 

Thomas.

 

PS: as you can see I’m not really familiar with MPI on Windows and compilation issues…