Eric, I think Toby is right. Except that PETSc installs all that you specify to configure as --download-package in $PETSC_DIR/$PETSC_ARCH/lib. There you will find libmpich**, whereas bins (such as mpiexec) in $PETSC_DIR/$PETSC_ARCH/bin. In the same spirit, includes are in $PETSC_DIR/$PETSC_ARCH/include
Stefano 2012/1/20 Toby D. Young <[email protected]> > > Eric, > > Short story: deal.II is not going to search your entire computer for an > mpi compatible compiler - he will search in the system directories only, > /usr/bin, and so on. (petsc is not in your default search path yet). You > need to help deal.II find those mpi compiler pieces if it is not installed > on your system, but just somewhere locally. > > > PETSC was configured as follows: > > > > ./configure --download-mpich=1 --download-hypre=1 > --with-shared-libraries=1 > > --with-x=0 -download-parmetis --download-scalapack --download-blacs > > > > Checking the config.log file, it appears that deal.II cannot find an > mpich > > library: > > > > ./conftest: error while loading shared libraries: libmpich.so.1.2: > cannot open > > shared object file: No such file or directory > > > > However, this library does not appear to exist on my computer despite > having > > just installed mpich2 with PETSC. There is a libmpich.so.3.3 in > > /path-to-petsc/petsc-arch/lib > > I remember that petsc "installs" mpich (and the hypre you downloaded) into > path-to-petsc/externalpackages/*. Petsc does not and can not install these > in to the system - and therefore they are not globally available for > deal.II to find yet. > > Try explicitly pointing deal.II to your mpich that petsc made for you. > Something like this should help: > > ./configure --enable-mpi CXX=path-to-petsc/externalpackages/??/mpich++ > CC=path-to-petsc/externalpackages/??/mpicc > > (I don't know if the --enable-mpi flag is needed here) > > If configure does work, the correct path should appear in > common/Make.global_options, where the compilers are listed (right at the > top). I have not tried to do this, I've always had system installed mpi > compilers - so I also do not know if that will be enough. > > Using Wolfgang's code bit can help too, except there you may have to put > in the full path to the mpicc petsc got for you, ie > > /home/../path-to-petsc/externalpackages/../mpicc x.c > > Use *full* paths all the time, and let us know if that works or not. > > Best, > Toby > > ----- > > Toby D. Young > Assistant Professor > > Institute of Fundamental Technological Problems > Polish Academy of Sciences > ul Adolfa Pawinskiego 5b > 02-106 Warsaw > Poland > > www: http://www.ippt.gov.pl/~tyoung > skype: stenografia > > _______________________________________________ > dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii > -- Stefano
_______________________________________________ dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii
