Robert, I'm sorry I don't really have time to dig into this at the moment but there are a few more things you can try. First if you just want to play around with libMesh you don't need to run with the MPI library. You might try disabling MPI when you run configure to see if that will provide a working serial build.
Another thing you might try is running the examples explicitly instead of using the make target. Go into one of the example directories and try running the executable directly. Try launching one of the examples both with and without using "mpiexec". Some MPI implementations are picky and won't run even a serial case properly if not launched with the launcher. I'll let you know if I think of anything else. Cody On Dec 15, 2010, at 12:18 PM, robert wrote: > Cody, > > here I also have the settings of Make.common > I used the libraries mpich2 and libpetsc3.0.0 from the Ubuntu > repository. > For me it is strange that it worked fine with the version which I > installed one year ago. Today I have just tried to install the new > libmesh release - I did not change anything else - at least not on > purpose. > Thanks for your help. > > Robert > > ############################################################################### > # the following lines will be replaced by the output > # of ./configure > hosttype = i686-pc-linux-gnu > hostos = linux-gnu > > libmesh_CXX = mpicxx > libmesh_CC = gcc > libmesh_F77 = > libmesh_F90 = gfortran > libmesh_LDFLAGS = > libmesh_DLFLAGS = > libmesh_LIBS = > libmesh_FLIBS = @FLIBS@ > libmesh_FFLAGS = > GXX-VERSION = gcc4.4 > libmesh_CXXSHAREDFLAG = -shared > libmesh_CSHAREDFLAG = -shared > libmesh_RPATHFLAG = -Wl,-rpath, > > # Use libmesh-specific compiler flags if available, otherwise > # use general compiler flags from environment > libmesh_CXXFLAGS ?= $(CXXFLAGS) > libmesh_CPPFLAGS ?= $(CPPFLAGS) > > # Complex variable support > enable-complex = no > > # Petsc iterative solvers for parallel and uniprocessor > # applications > enable-petsc = yes > petsc-version = 3.0.0 > petsc-major = 3 > petsc-major-minor = 3.0.x > PETSC_ARCH = linux-gnu-c-opt > PETSC_DIR = /usr/lib/petsc > > # Slepc for eigen value analysis > enable-slepc = no > SLEPC_DIR = /usr/lib/slepc > > # MPI configuration > # (only explicitly defined when PETSc is absent, otherwise snooped from > PETSc) > MPI_IMPL = petsc_snooped > MPI_INCLUDE = > MPI_LIB = > > # Trilinos configuration > enable-trilinos = no > AZTECOO_MAKEFILE_EXPORT = > > # Nox configuration > enable-nox = no > NOX_MAKEFILE_EXPORT = > > # Doxygen for generating documentation > doxygen = > > # Perl for making .depend > perl = /usr/bin/perl > > # Flag for optional packages > enable-optional = yes > enable-laspack = yes > enable-metis = yes > enable-parmetis = yes > enable-sfcurves = yes > enable-gzstream = yes > enable-tetgen = yes > enable-triangle = yes > enable-gmv = yes > enable-vtk = yes > enable-glpk = no > enable-exodus = yes > enable-netcdf = yes > enable-nemesis = yes > enable-libhilbert = yes > > # > # Set the current directory. > libmesh_dir := /usr/include/libmesh-0.7.0.3 > export libmesh_dir > ############################################################################### > > > > > > > > > > > > Am Mittwoch, den 15.12.2010, 08:18 -0700 schrieb Cody Permann: >> Robert, I have been running libMesh on Ubuntu every release since 8.04. We >> have it running right now on 10.10 without any issues. The one thing that >> we do slightly different than many users though is that we build our own >> MPICH2 library to link against instead of using the packages available >> through Ubuntu. Please post your configure options for libMesh and any >> other packages you build against and we'll see if there are any obvious >> issues. >> >> Cody >> >> >> On Dec 15, 2010, at 8:08 AM, robert wrote: >> >>> Hi, >>> >>> I have just tried to install the latest libmesh release in Ubuntu >>> karmic. I just downloaded the folder and used ./configure and make to >>> install libmesh. >>> However, when I want to do >>> make run_examples >>> I get the following error message: >>> >>> Fatal error in MPI_Comm_dup: Invalid communicator, error stack: >>> MPI_Comm_dup(168): MPI_Comm_dup(comm=0x42ba2940, new_comm=0x4073b98c) >>> failed >>> MPI_Comm_dup(96).: Invalid communicator >>> make[2]: *** [run] Fehler 1 >>> make[2]: Verlasse Verzeichnis >>> '/usr/include/libmesh-0.7.0.3/examples/ex0' >>> make[1]: *** [run] Fehler 1 >>> make[1]: Verlasse Verzeichnis '/usr/include/libmesh-0.7.0.3/examples' >>> make: *** [run_examples] Fehler 2 >>> >>> >>> Before I used some oder version of libmesh and everything worked fine. >>> >>> thanks, >>> Robert >>> >>> >>> ------------------------------------------------------------------------------ >>> Lotusphere 2011 >>> Register now for Lotusphere 2011 and learn how >>> to connect the dots, take your collaborative environment >>> to the next level, and enter the era of Social Business. >>> http://p.sf.net/sfu/lotusphere-d2d >>> _______________________________________________ >>> Libmesh-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/libmesh-users >> > > ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
