Arvind, I also use Debian (Etch) and I had similar problems when I compiled Libmesh for the first times. Even recently I had problems with slepc (in debug mode). Here are a few "recipes" that makes it all work fine for me:
First install libMesh dependencies from Debian repositories: -mpich -blas -lapack -some fortran compiler (g77) -zlib (if you want to use that option in libmesh) Download version 2.3.2 of PETSc and SLEPc (the latest patch versions are ok). Download libmesh from SVN. I had problems to run libmesh+petsc+slepc in debug mode. The compilation is ok but all the examples abort with a problem related to petsc (even if that example doesn't use slepc at all, like example1). I can give more information about this if anyone is interested. So I have two versions (debug, optimized) of everything (libmesh, petsc, slepc), but slepc only works in optimized mode. ------------------------------------------------------------------------------------------ * OPTIMIZED MODE * First compile PETSc: export PETSC_DIR=/petsc/dir; export PETSC_ARCH=linux-gnu-opt cd $PETSC_DIR ./config/configure.py --with-blas-lapack-dir=/usr/lib --with-mpi-dir=/usr/lib/mpich --with-debugging=no --with-shared make all make test Then compile SLEPc: export SLEPC_DIR=/slepc/dir; export SLEPC_ARCH=linux-gnu-opt cd $SLEPC_DIR ./config/configure.py make make test Finally compile libMesh export METHOD=opt ./configure --enable-shared=yes --enable-exceptions=yes --enable-everything=no --enable-tracefiles=no --enable-amr=yes--enable-vsmoother=yes --enable-periodic=yes --enable-parmesh=no --enable-2D-only=no --enable-pfem=yes --enable-ifem=yes --enable-second=yes --enable-xdr=yes --enable-complex=no --enable-reference-counting=no --enable-perflog=no --enable-petsc=yes --enable-slepc=yes --enable-trilinos=no --enable-tbb=no --enable-laspack=yes --enable-sfc=yes --enable-gzstreams=yes --enable-bzip2=yes --enable-tecplot=no --enable-metis=yes --enable-parmetis=yes --enable-tetgen=yes --enable-triangle=yes --enable-gmv=yes --enable-vtk=yes --enable-netcdf=yes --enable-exodus=yes --enable-libHilbert=yes --with-vtk-include=/usr/include/vtk-5.0 --with-vtk-lib=/usr/lib make ------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------ * DEBUG MODE * Compile PETSc: export PETSC_DIR=/petsc/dir; export PETSC_ARCH=linux-gnu-opt cd $PETSC_DIR ./config/configure.py --with-blas-lapack-dir=/usr/lib --with-mpi-dir=/usr/lib/mpich --with-debugging=yes --with-shared make all make test Compile libMesh export METHOD=dbg ./configure --enable-shared=yes --enable-exceptions=yes --enable-everything=no --enable-tracefiles=no --enable-amr=yes--enable-vsmoother=yes --enable-periodic=yes --enable-parmesh=no --enable-2D-only=no --enable-pfem=yes --enable-ifem=yes --enable-second=yes --enable-xdr=yes --enable-complex=no --enable-reference-counting=yes --enable-perflog=yes --enable-mpi=yes --enable-petsc=yes --enable-slepc=no --enable-trilinos=no --enable-tbb=no --enable-laspack=yes --enable-sfc=yes --enable-gzstreams=yes --enable-bzip2=yes --enable-tecplot=no --enable-metis=yes --enable-parmetis=yes --enable-tetgen=yes --enable-triangle=yes --enable-gmv=yes --enable-vtk=yes --enable-netcdf=yes --enable-exodus=yes --enable-libHilbert=yes --with-mpi=/usr/lib/mpich --with-vtk-include=/usr/include/vtk-5.0 --with-vtk-lib=/usr/lib make ------------------------------------------------------------------------------------------ Of course you should add the environment variables correspondent to the mode you use more often to .bashrc. Compilation in optimized mode is faster, so I use it when I'm still in the edit-compile phase. Then I switch to debug mode to test for more delicate problems. Hope this helps. Paulo PS: i can add this information to the installation page in the wiki. How do I create an account to add content? PPS: there's a typo in this page: http://libmesh.sourceforge.net/installation.php: "Valid values for METHOD are opt [...] debug". The value should be "dbg", not "debug". >Message: 3 >Date: Thu, 10 Jul 2008 15:52:57 +0530 >From: "Arvind Ajoy" <[EMAIL PROTECTED]> >Subject: [Libmesh-users] Compilation problems using latest SVN trunk and >libmesh 0.6.2 > >Dear Developers and Users, > >Firstly, thank you for this piece of software! I have been using the Debian >package for a month now, and have been impressed with its capabilities. >However, >since I need to enable VTK and SLEPc, I have been trying to compile libmesh >from >sources. I need SLEPc since I am trying to solve aome quantum physics problems. >This is resulting in errors which I list below. > >Some details regarding my configuration ( the computer is a Pentium D >system) >(a) gcc-4.2 and g++-4.2 for compilation. >(b) mpich 1.2.7 installed from debian repo. >(c) Compiled Petsc-2.3.3-p13 from source with the following config : > config/configure.py --with-cc=gcc --with-cxx=g++ --with-fc=g77 > --with-mpi-dir=/usr/lib/mpich/ > --with-debugging=1 --with-shared >(d)Compiled Slepc-2.3.3(including latest patches) from source. >(e)Libmesh config : ./configure --prefix=/usr/local/libmesh --enable-slepc > --enable-vtk --with-vtk-include=/usr/include/vtk-5.0 > ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
