Hello- I certainly agree it would be infinitely faster! =) But, it seems that since I'm compiling in debug, those flags shouldn't be there anyway, and thus it seems like the wrong fix.
Actually, I should point out I didn't try that suggestion because I didn't see any IPO flags anywhere to turn off. grep-ing the whole directory for ipo or IPO only returned one line in the configure file in a comment where it was deleting information from the IPO. It did compile fine in optimize mode. So, then I wondered if it was flags in PETSc that were conflicting because I was just using the default petsc/3.2 module. So, I then tried it with petsc/3.2-debug but got the same error. Here is the screen output from configure. Would you need the configure.log as well? Thanks! Andrea --------------------------------------------- ----------- Configuring libMesh ------------- --------------------------------------------- checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking for mpicxx... mpicxx checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether mpicxx accepts -g... yes <<< C++ compiler is Intel(R) icc 11 >>> checking for mpicc... mpicc checking whether we are using the GNU C compiler... yes checking whether mpicc accepts -g... yes checking for mpicc option to accept ISO C89... none needed checking for mpif90... mpif90 checking whether we are using the GNU Fortran compiler... no checking whether mpif90 accepts -g... yes checking for mpif77... mpif77 checking whether we are using the GNU Fortran 77 compiler... no checking whether mpif77 accepts -g... yes <<< Default floating point is double precision (double) >>> checking for C/C++ restrict keyword... __restrict <<< Configuring library with getpwuid >>> <<< Configuring library with exception throwing support >>> checking how to run the C++ preprocessor... mpicxx -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking size of short int... 2 checking size of int... 4 checking size of unsigned int... 4 checking size of long int... 8 checking size of float... 4 checking size of double... 8 checking size of void *... 8 checking size of function_pointer... 8 configuring size of subdomain_id... 2 checking whether the compiler supports Run-Time Type Identification... yes checking getopt.h usability... yes checking getopt.h presence... yes checking for getopt.h... yes checking csignal usability... yes checking csignal presence... yes checking for csignal... yes checking sys/resource.h usability... yes checking sys/resource.h presence... yes checking for sys/resource.h... yes checking whether the compiler implements namespaces... yes checking whether the compiler has locale... yes checking whether the compiler has stringstream... yes checking whether the compiler supports std::unordered_multimap... no checking whether the compiler supports std::tr1::unordered_multimap... yes checking whether the compiler supports std::unordered_map... no checking whether the compiler supports std::tr1::unordered_map... yes checking whether the compiler supports std::unordered_set... no checking whether the compiler supports std::tr1::unordered_set... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking whether the compiler supports GCC C++ ABI name demangling... yes checking whether the c++ compiler supports glibc backtrace... yes checking for boostlib >= 1.20.0... configure: We could not detect the boost libraries (version 1.20 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in <boost/version.hpp>. See http://randspringer.de/boost for more documentation. <<< External boost installation *not* found... will try to configure for libmesh's internal boost >>> checking for boostlib >= 1.20.0... yes <<< Using libmesh-provided boost in ./contrib >>> <<< Configuring library with stack trace file support >>> <<< Configuring library with AMR support >>> <<< Configuring library with variational smoother support >>> <<< Configuring library with periodic BC support >>> <<< Configuring library with Dirichlet constraint support >>> <<< Configuring library with node constraints support >>> <<< Configuring library to use ghosted local vectors >>> <<< Configuring library with higher order p-FEM shapes >>> <<< Configuring library with infinite elements >>> <<< Configuring library with second derivatives >>> checking rpc/rpc.h usability... yes checking rpc/rpc.h presence... yes checking for rpc/rpc.h... yes checking for xdrstdio_create... yes <<< Configuring library with XDR support >>> <<< Configuring library with real number support >>> <<< Configuring library with reference counting support >>> <<< Configuring library with performance logging support >>> --------------------------------------------- ----- Configuring for optional packages ----- --------------------------------------------- <<< Configuring library with MPI from PETSC config >>> <<< Configuring library with PETSc version 3.2.0 support >>> <<< Configuring library with Hypre support >>> <<< Invalid "$SLEPC_DIR" detected (slepc.h not found). SLEPc disabled. >>> checking tbb/task_scheduler_init.h usability... no checking tbb/task_scheduler_init.h presence... no checking for tbb/task_scheduler_init.h... no checking for tbb/task_scheduler_init.h... (cached) no checking for thread local storage (TLS) class... __thread <<< Configuring library with LASPACK version 1.12.3 support >>> checking how to run the C preprocessor... mpicc -E checking sfcurves.h usability... yes checking sfcurves.h presence... yes checking for sfcurves.h... yes <<< Configuring library with SFC support >>> checking zlib.h usability... yes checking zlib.h presence... yes checking for zlib.h... yes checking for gzopen in -lz... yes checking gzstream.h usability... yes checking gzstream.h presence... yes checking for gzstream.h... yes checking for bzip2... bzip2 checking for bunzip2... bunzip2 <<< Using bzip2/bunzip2 for writing/reading compressed .bz2 files >>> checking for xz... xz <<< Using xz for writing/reading compressed .xz files >>> checking for ./contrib/tecplot/lib/x86_64-unknown-linux-gnu/tecio.a... yes checking TECIO.h usability... yes checking TECIO.h presence... yes checking for TECIO.h... yes <<< Configuring library with Tecplot API support >>> checking metis.h usability... yes checking metis.h presence... yes checking for metis.h... yes <<< Configuring library with Metis support >>> checking parmetis.h usability... yes checking parmetis.h presence... yes checking for parmetis.h... yes <<< Configuring library with ParMetis support >>> checking for doxygen... /usr/bin/doxygen checking for dot... no <<< Configuring library with TetGen support >>> <<< Configuring library with Triangle support >>> <<< Configuring library with GMV support >>> checking /vtkConfigure.h usability... no checking /vtkConfigure.h presence... no checking for /vtkConfigure.h... no VTK header files not found! checking /usr/include/Eigen/Eigen usability... no checking /usr/include/Eigen/Eigen presence... no checking for /usr/include/Eigen/Eigen... no Eigen header files not found! checking /usr/include/glpk.h usability... no checking /usr/include/glpk.h presence... no checking for /usr/include/glpk.h... no GLPK header files not found! <<< Configuring library with Netcdf support >>> <<< Configuring library with Exodus API support >>> <<< Configuring library with Nemesis API support >>> <<< Configuring library with libHilbert support >>> <<< Configuring library with fparser support >>> ---------------------------------------------- --- Done configuring for optional packages --- ---------------------------------------------- checking for perl... /usr/bin/perl configure: creating ./config.status config.status: creating Make.common On Fri, Mar 30, 2012 at 7:10 PM, Kirk, Benjamin (JSC-EG311) <benjamin.kir...@nasa.gov> wrote: > And seeing as how you are building in debug mode I wonder how you got ipo in > the first place? In fact it could be that debug aggressive flags and ipo > conflict in the compiler in some known way because no one ever does that! > > So how did they get there I wonder... Is this a case of a tacc mpicxx setting > optimized flags internally? > > Or could it be that it found different c and cxx compilers... > > Hmm - could you post the output from configure? > > -Ben > > > > On Mar 30, 2012, at 9:04 PM, "John Peterson" <jwpeter...@gmail.com> wrote: > >> On Fri, Mar 30, 2012 at 6:19 PM, Andrea Hawkins-Daarud >> <andjhawk...@gmail.com> wrote: >>> Hello- >>> >>> Yesterday I svn up-ed on lonestar but the build crashed unexpectedly. >>> >>> I'm running with intel/11 compilers and petsc/3.2. >>> >>> It compiles all the C++ ok, but then on the first C file I get the >>> following: >>> >>> ... >>> Compiling C++ (in debug mode) src/utils/utility.C... >>> Compiling C++ (in debug mode) src/utils/xdr_cxx.C... >>> Compiling C (in debug mode) src/base/libmesh_isnan.c... >>> Linking >>> /home1/00639/ahawkins/libmesh/lib/x86_64-unknown-linux-gnu_dbg/libmesh.so >>> (0): internal error: backend signals >>> >>> icpc: error #10014: problem during multi-file optimization compilation >>> (code 4) >>> make: *** >>> [/home1/00639/ahawkins/libmesh/lib/x86_64-unknown-linux-gnu_dbg/libmesh.so] >>> Error 4 >>> >>> >>> I found a suggestion for a fix involving turning off WPO and adding >>> "/Qipo-" to the compiler command line here: >>> http://software.intel.com/en-us/forums/showthread.php?t=62727 >>> >>> But, that seems more drastic than I would prefer. Is there another >>> obvious thing I'm missing? >> >> IPO is a more aggressive form of optimization, I don't think it will >> hurt you too bad to turn it off... >> >> And your code will be infinitely faster running if it compiles :) >> >> -- >> John >> >> ------------------------------------------------------------------------------ >> This SF email is sponsosred by: >> Try Windows Azure free for 90 days Click Here >> http://p.sf.net/sfu/sfd2d-msazure >> _______________________________________________ >> Libmesh-users mailing list >> Libmesh-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/libmesh-users ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
