On Mar 8, 2013, at 9:25 AM, Jonathan Guyer wrote:
> On Mar 7, 2013, at 2:53 PM, Adrian Jacobo wrote:
>
>> On a related comment, I'm able to compile your example code using the openmp
>> wrapper for gcc:
>>
>> openmpicc trivialmpi.c -o trivialmpi
>>
>> and it runs just fine using openmpirun.
>
> This is the macports openmpi you installed? That may be the problem. At least
> in Snow Leopard, openmpi is provided by the Apple Developer Tools (XCode) and
> Trilinos' cmake found /usr/bin/mpicc and /usr/bin/mpiexec without guidance
> from me.
With a bit of further googling, it appears that Apple has ceased providing
OpenMPI as of either Lion or Mountain Lion.
The fact examples/parallel.py fails tells me that mpi4py and PyTrilinos may not
be linked against the same MPI installation. One way to check this is to run
`otool -L` on the respective compiled libraries. For me:
$ python -c "import mpi4py; print mpi4py.__file__"
/Users/guyer/.virtualenvs/virtualbrew/lib/python2.7/site-packages/mpi4py/__init__.pyc
$ ls /Users/guyer/.virtualenvs/virtualbrew/lib/python2.7/site-packages/mpi4py
MPE.so __init__.py __init__.pyo include rc.py
rc.pyo
MPI.so __init__.pyc dl.so mpi.cfg rc.pyc
$ otool -L
/Users/guyer/.virtualenvs/virtualbrew/lib/python2.7/site-packages/mpi4py/MPI.so
/Users/guyer/.virtualenvs/virtualbrew/lib/python2.7/site-packages/mpi4py/MPI.so:
/usr/lib/libmpi.0.dylib (compatibility version 1.0.0, current version
1.0.0)
/usr/lib/libopen-rte.0.dylib (compatibility version 1.0.0, current
version 1.0.0)
/usr/lib/libopen-pal.0.dylib (compatibility version 1.0.0, current
version 1.0.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version
830.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 125.2.11)
$ python -c "import PyTrilinos; print PyTrilinos.__file__"
/Users/guyer/.virtualenvs/virtualbrew/lib/python2.7/site-packages/PyTrilinos/__init__.pyc
$ ls
/Users/guyer/.virtualenvs/virtualbrew/lib/python2.7/site-packages/PyTrilinos
Amesos.py EpetraExt.py ML.py
Teuchos.pyc _Galeri.so __init__.pyc
Amesos.pyc EpetraExt.pyc ML.pyc
TriUtils.py _IFPACK.so typed_dict.py
Anasazi.py Galeri.py NOX
TriUtils.pyc _Komplex.so typed_dict.pyc
Anasazi.pyc Galeri.pyc Pliris.py
_Amesos.so _ML.so typed_list.py
AztecOO.py IFPACK.py Pliris.pyc
_Anasazi.so _Pliris.so typed_list.pyc
AztecOO.pyc IFPACK.pyc PropertyBase.py
_AztecOO.so _Teuchos.so typed_tuple.py
Epetra.py Komplex.py PropertyBase.pyc
_Epetra.so _TriUtils.so typed_tuple.pyc
Epetra.pyc Komplex.pyc Teuchos.py
_EpetraExt.so __init__.py
$ otool -L
/Users/guyer/.virtualenvs/virtualbrew/lib/python2.7/site-packages/PyTrilinos/_Epetra.so
/Users/guyer/.virtualenvs/virtualbrew/lib/python2.7/site-packages/PyTrilinos/_Epetra.so:
:
:
/usr/lib/libmpi_cxx.0.dylib (compatibility version 1.0.0, current
version 1.0.0)
/usr/lib/libmpi.0.dylib (compatibility version 1.0.0, current version
1.0.0)
/usr/lib/libopen-rte.0.dylib (compatibility version 1.0.0, current
version 1.0.0)
/usr/lib/libopen-pal.0.dylib (compatibility version 1.0.0, current
version 1.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.9.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 125.2.0)
So you can see that both packages are linked against /usr/lib/libmpi.0.dylib on
my system (as well as a other common libraries).
You should see a similar consistency, but I'm guessing you won't. Tell us what
you get and we'll try and figure out how to proceed.
_______________________________________________
fipy mailing list
[email protected]
http://www.ctcms.nist.gov/fipy
[ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
