Thanks for your quick response. I attached the makecheck.log to my first email. I changed the compilers to mpi. These are included in the petsc directory (I downloaded it from the configure options in petsc) My ./configure command line appears as follows:
./configure --enable-mpi --enable-amr --enable-vsmoother --enable-dirichlet --enable-nodeconstraint --enable-parmesh --enable-pfem --enable-ifem --enable-second --enable-examples --enable-boost --enable-petsc --enable-periodic --enable-tetgen --enable-triangle --enable-vtk --with-boost=/usr/local --with-mpi=/home/miguel/petsc-3.4.4/externalpackages/openmpi-1.6.4 --with-vtk-include=/usr/local/include/vtk-6.1 --with-vtk-lib=/usr/local/lib/ --disable-slepc --disable-pthreads --with-cxx=/home/miguel/petsc-3.4.4/arch-linux2-c-debug/bin/mpicxx --with-cc=/home/miguel/petsc-3.4.4/arch-linux2-c-debug/bin/mpicc My config.log doesn't have new errors, but when I type make. I get this: Making all in exodusii/v5.22/exodus make[2]: Entering directory `/home/miguel/libmesh/contrib/exodusii/5.22b/exodus' PPF77 forbind/src/libdbg_la-addrwrap.lo -------------------------------------------------------------------------- No underlying compiler was specified in the wrapper compiler data file (e.g., mpicc-wrapper-data.txt) I searched for this file and inside of the petsc directory, I find two: /home/miguel/petsc-3.4.4/externalpackages/openmpi-1.6.4/ompi/tools/wrappers/mpicc-wrapper-data.txt /home/miguel/petsc-3.4.4/arch-linux2-c-debug/share/openmpi/mpicc-wrapper-data.txt Both of them are identical to this: # There can be multiple blocks of configuration data, chosen by # compiler flags (using the compiler_args key to chose which block # should be activated. This can be useful for multilib builds. See the # multilib page at: # https://svn.open-mpi.org/trac/ompi/wiki/compilerwrapper3264 # for more information. project=Open MPI project_short=OMPI version=1.6.4 language=C compiler_env=CC compiler_flags_env=CFLAGS compiler=gcc extra_includes= preprocessor_flags= compiler_flags=-pthread linker_flags= libs=-lmpi -ldl -lm -Wl,--export-dynamic -lrt -lnsl -lutil -lm -ldl required_file= includedir=${includedir} libdir=${libdir} Should I change something in this file? Thanks in advance. On Wed, May 14, 2014 at 11:29 AM, Roy Stogner <[email protected]>wrote: > > On Wed, 14 May 2014, Miguel Angel Salazar de Troya wrote: > > I am using petsc 3.4-4 and gcc 4.7. I have gcc 4.8 installed by default, >> by >> I thought I would change to 4.7 since it is the last version you guys >> tested libmesh with (as it appears in the website). >> > > Gah, thanks for the information. We need to update the website; I've > been using libMesh successfully with gcc-4.8 for a while, and once > with whatever gcc-4.9-pre version is available in the Ubuntu PPAs. > > > I highlight here some of the errors I get during the configuration stage: >> >> gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-7ubuntu3) >> configure:5662: $? = 0 >> configure:5651: /usr/bin/gcc-4.7 -V >&5 >> gcc-4.7: error: unrecognized command line option '-V' >> gcc-4.7: fatal error: no input files >> compilation terminated. >> configure:5662: $? = 4 >> configure:5651: /usr/bin/gcc-4.7 -qversion >&5 >> gcc-4.7: error: unrecognized command line option '-qversion' >> gcc-4.7: fatal error: no input files >> compilation terminated. >> > > These aren't actually errors; configure is just autodetecting which > compiler flags your compiler does and doesn't support. > > > configure:10667: /usr/bin/gcc-4.7 -E conftest.c >> conftest.c:12:28: fatal error: ac_nonexistent.h: No such file or directory >> > > This is an *intentional* error; configure is making sure that your > compiler gives a failure code on exit when the preprocessor fails. > > > In file included from /usr/include/c++/4.8/unordered_map:35:0, >> from conftest.cpp:56: >> /usr/include/c++/4.8/bits/c++0x_warning.h:32:2: error: #error This file >> requires compiler and library support for the ISO C++ 2011 standard. This >> support is currently experimental, and must be enabled with the -std=c++11 >> or -std=gnu++11 compiler options. >> > > This *probably* isn't an error; we test for compiler/STL support for > several different versions of hash table based containers, and on > recent gcc versions this particular hash table should indeed only be > enabled when using C++11. > > > The makecheck.log also includes some errors that prompted me to write this >> email. >> > > Send us those? We still might have to back up into the configure logs > to figure out what caused them, but at least in "make" there shouldn't > be any expected errors to distract from whatever the real problem is. > --- > Roy > -- *Miguel Angel Salazar de Troya* Graduate Research Assistant Department of Mechanical Science and Engineering University of Illinois at Urbana-Champaign (217) 550-2360 [email protected] ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
