Cody Permann wrote: > Do any of the libMesh developers actually "install" Petsc-3.0? That is, does > anybody in this group run "make install" after successfully building Petsc? > The reason I ask is that I typically do install Petsc on our shared cluster > systems to keep the source and the compiled libraries separate for a number > of reasons. As far as I can tell, libMesh configure does not get the paths > correct for installed versions of Petsc-3.0. libMesh configure works fine > though when you point PETSC_DIR at Petsc build tree. It appears that > Petsc-3.0 has moved away from the configuration $PETSC_DIR/lib/$PETSC_ARCH in > favor of a completely flat install directory like this: > $PETSC_DIR/lib/<petsclibs> > > I tried unsetting the $PETSC_ARCH variable which seems to have been relegated > to configuration and building only in the newer version. I don't believe you > need PETSC_ARCH set for running anymore (I could be wrong here). This > observation is based upon the message received when running make install. > Note the instructions to unset PETSC_ARCH before running the tests... > > ==================================== > If using sh/bash, do the following: > PETSC_DIR=/Users/permcj/root/usr/local/packages/petsc/petsc-3.0.0-p11; > export PETSC_DIR > unset PETSC_ARCH > If using csh/tcsh, do the following: > setenv PETSC_DIR /Users/permcj/root/usr/local/packages/petsc/petsc-3.0.0-p11 > unsetenv PETSC_ARCH > Run the following to verify the install (remain in current directory for the > tests): > make test > ==================================== > > The new system is a more consistent with most other libraries that one would > install on a typical system which is nice. I'll take a stab at getting the > configuration right inside of the m4 files unless somebody thinks I may be > making a fundamental mistake here. > > Thanks, > Cody > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Libmesh-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-devel > > I am a user and my libmesh v0.6.4 works well with Petsc3.0 after configuring PETSC_ARCH path, but the machine is a 4-core desktop not cluster.
Liang ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
