| Thread Previous • Date Previous • Date Next • Thread Next |
On Mon 2008-06-02 08:29, Johannes Ring wrote: > On Fri, May 30, 2008 Nuno David Lopes wrote: > > Ok, i have mpich on my system, petsc (without hypre) compiled > > with --download-mpich=1, it all works, my code compiles and runs etc.... > > Everything is running with the exception that MPI isn't working... > > > > ..................scons: Reading SConscript files ... > > Using options from scons/options.cache > > MPI not found (might not work if PETSc uses MPI). > > ........................................................................ > > The reason you get this warning is that we are unable to locate mpirun or > an MPI C++ compiler (we look for mpic++, mpicxx, and mpiCC) on your > system. This might be a bit limiting, so I added mpiexec and orterun as > alternatives for mpirun. Please try again with the latest from the hg > repository. When PETSc installs mpich, it doesn't automatically put it in your path so you will have to specify the path explicitly when you configure Dolfin. In terms of Dolfin configuration, it's not really a good idea to just use any random MPI implementation that may be in your path. You can get the correct implementation from PETSc (CC,CXX,MPIEXEC in $PETSC_DIR/bmake/$PETSC_ARCH/petscconf). This would be especially nice if you have multiple PETSc builds with different MPI implementations (i.e. OpenMPI with a debugging build for development/testing and vendor MPI with optimized build for production runs). Jed
Attachment:
pgp8wYzXTHrex.pgp
Description: PGP signature
| Thread Previous • Date Previous • Date Next • Thread Next |
