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 ________________________________(_)_\(_)_______________