From: Roy S. <roy...@ic...> - 2007-07-02 22:07:03
|
On Mon, 2 Jul 2007, John Peterson wrote: > Tahar Amari writes: > > Hi John > > > > I opened the file > > > > > $PETSC_DIR/bmake/$PETSC_ARCH/petscconf > > > > and found > > > > MPI_LIB = -L/usr/local/mpich/lib -L/usr/local/mpich/lib -lfmpich - > > lmpich -lpmpich -lmpich -lpmpich -lpmpich > > > > So , is what you thought really happening ? > > Well, it's not blank as I had guessed, and it doesn't really look > "wrong", just a little strange. The library names shouldn't be > repeated multiple times like that. And note that if you are > linking against shared (.so) libraries, "/usr/local/mpich/lib" > must be in your LD_LIBRARY_PATH, or whatever the equivalent is > on Mac OSX. But the MPI_LIB variable in PETSc still isn't being used correctly by libMesh, right? The MPI_LIB and MPI_INCLUDE variables in Make.common are blank? First try copying the PETSc versions of those variables and see what happens. The multiple library names are PETSc's problem, and won't hurt anything. And with --disable-shared the library path isn't a problem. Let's first see if hand-setting the MPI variables in Make.common fixes things, and if so then we can try and figure out why they aren't being autodetected by either snooping PETSc or by manually setting an MPI directory. --- Roy |