On Mar 29, 2011, at 12:06 PM, Jacek Hoffman wrote:
> > Hi all, > I'm using FiPy on Debian GNU/Linux. > There is a problem with python 2.6 as follows: > > > jacek@computer01:~$ python2.6 > Python 2.6.6 (r266:84292, Dec 27 2010, 00:02:40) > [GCC 4.4.5] on linux2 > Type "help", "copyright", "credits" or "license" for more information. >>>> from fipy import * > *** The MPI_comm_size() function was called before MPI_INIT was invoked. > *** This is disallowed by the MPI standard. > *** Your MPI job will now abort. > [computer01:3181] Abort before MPI_INIT completed successfully; not able > to guarantee that all other processes were killed! > > > Fortunately I have also python 2.5 installed and when invoking FiPy from > it everything works as expected except Trilinos (it needs python2.6). > I believe the above is not specific to Debian, reveals rather some changes > in python modules. > So far using FiPy with python 2.5 and without Trilinos is OK for me, > however I'm worrying about future compatibility. Or there are some > environmental variables for parallel computing what need proper setting. FiPy certainly works with Python 2.6, although I don't know that we've tested it on Debian. There are no particular environment variables you should need to set, although depending on how you have installed things, you might need to set LD_LIBRARY_PATH or something; this should be explained by the respective packages, though (MPI, Trilinos, mpi4py). If I had to guess, some of your packages (PyTrilinos or mpi4py) are not compiled against the same MPI library as each other or as the one available to you at runtime, but it's not clear to me where the error is coming from. What happens when you do python2.6 -c "from mpi4py import MPI" and python2.6 -c "from PyTrilinos import Epetra" ? For completeness: What Debian release? What version of FiPy? What python packages do you have installed?
