Awesome, so it looks like it worked?
Yup. All systems go on Ranger, at least with the Intel compilers I prefer to use. And I have been running out of the mpi4py trunk for a while now on Ranger, which hasn't changed for six months (see below).
And you said you were having problems on Kraken, yes? Was that with 0.6.0 or with trunk?
That was with trunk, the same version that I checked out on Ranger. sskory@kraken-pwd1:~/mpi4py-test> svn info Path: . URL: http://mpi4py.scipy.org/svn/mpi4py/mpi4py/trunk Repository Root: http://mpi4py.scipy.org/svn/mpi4py Repository UUID: 5e30ba94-2d20-0410-ad46-dcadf819b77c Revision: 180 Node Kind: directory Schedule: normal Last Changed Author: dalcinl Last Changed Rev: 179 Last Changed Date: 2008-06-02 14:25:05 -0400 (Mon, 02 Jun 2008) Here's the output: http://paste.enzotools.org/show/29/ It looks like I may just need to link to the correct mpi library/includes to get this to work. However, Matt, I'm still puzzled why you can get yours to work but not mine. There has to be a difference in our environments and modules on Kraken. sskory@kraken-pwd1:~/mpi4py-test> module list Currently Loaded Modulefiles: 1) modules/3.1.6 14) Base-opts/2.0.62 2) MySQL/4.0.27 15) PrgEnv-gnu/2.0.62 3) torque/2.3.0 16) xt-asyncpe/1.0 4) moab/5.2.2 17) xt-pe/2.0.62 5) xt-binutils-quadcore/2.0.0 18) xt-mpt/3.0.0 6) xtpe-quadcore 19) xt-libsci/10.2.1 7) xt-service/2.0.62 20) xt-totalview/8.4.1b 8) xt-libc/2.0.62 21) totalview-support/1.0.5 9) xt-os/2.0.62 22) gcc/4.2.0.quadcore 10) xt-catamount/2.0.62 23) subversion/1.4.6 11) xt-boot/2.0.62 24) imagemagick/6.4.2 12) xt-lustre-ss/2.0.62 25) java/jdk1.6.0_05 13) xtpe-target-cnl 26) globus/4.0.7 I'm pretty sure I'm using the same gcc (4.2.0) as I used to compile python, but I'm not at the point where that should make any difference, of course. _______________________________________________________ sskory@physics.ucsd.edu o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_\(_)_______________
Yup. All systems go on Ranger, at least with the Intel compilers I prefer to use. And I have been running out of the mpi4py trunk for a while now on Ranger, which hasn't changed for six months (see below).
right, because they moved to google code for the incompatible changes. :) (see URL above)
It looks like I may just need to link to the correct mpi library/includes to get this to work. However, Matt, I'm still puzzled why you can get yours to work but not mine. There has to be a difference in our environments and modules on Kraken.
Oh! Try setting mpicc = cc and mpicxx = CC in your mpi.cfg. That was the only thing I had to do... -Matt
right, because they moved to google code for the incompatible changes.
:) (see URL above)
Dood, so which version do you want us to download? On the page you sent us, there is: "svn co http://mpi4py.scipy.org/svn/mpi4py/mpi4py/trunk mpi4py" Is that the version you want us to dowload? If not, could you tell me exactly which version and what link to download from?
Oh! Try setting mpicc = cc and mpicxx = CC in your mpi.cfg. That was the only thing I had to do...
Hrm. Progress, but not there yet: http://paste.enzotools.org/show/30/ _______________________________________________________ sskory@physics.ucsd.edu o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_\(_)_______________
Dood, so which version do you want us to download? On the page you sent us, there is:
"svn co http://mpi4py.scipy.org/svn/mpi4py/mpi4py/trunk mpi4py"
Is that the version you want us to dowload? If not, could you tell me exactly which version and what link to download from?
You're right; I missed it completely. This is where you should get the download info: http://code.google.com/p/mpi4py/source/checkout so: svn checkout http://mpi4py.googlecode.com/svn/trunk/ mpi4py-read-only
I had this problem and solved it -- I will let you know when I can find my notes about it... -Matt
svn checkout http://mpi4py.googlecode.com/svn/trunk/ mpi4py-read-only
Ranger: I checked this out, installed Cython, and this seemed to 'python setup.py build' just fine. Lots of Intel warnings/remarks, as before.
I had this problem and solved it -- I will let you know when I can find my notes about it...
Kraken: I did the same as on Ranger, and now I get the same error as in paste 30 above with the newer mpi4py. _______________________________________________________ sskory@physics.ucsd.edu o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_\(_)_______________
Kraken: I did the same as on Ranger, and now I get the same error as in paste 30 above with the newer mpi4py.
Ugh, okay. I am actually playing with this stuff right now, and not having any luck. It's something about (I think) targetting catamount, which gets you the shared libraries (the real problem here.) If you can figure it out -- which combo of modules to load to link against shared libs -- let me know? I'm not sure I'll get to finish this today; spending the afternoon writing. -Matt
participants (2)
-
Matthew Turk
-
Stephen Skory