Re: [Libmesh-users] Compiler error using ICC ( partitioner_factory.C )

[Kirk, B. (JSC-EG311) <ben...@na...>]

Nope.  What version of the intel compilers, and does it happen in optimized
mode?

Usually our problems with icc have been in the other direction - they break
when aggressive optimization is turned on.

One thing to try before bugging intel, though - try adding -fpic to the
compile flags.  This is switched on by libMesh to generate
position-independent code as required for shared libraries.

-Ben

On 6/4/09 2:34 PM, "Brent Kraczek" <bkr...@ic...> wrote:

> I am attempting to compile libmesh on a cluster that uses mvapich and
> icc , but I keep getting a compiler error. I don't know if this is
> something you have seen before or if there is a work-around, short of
> asking Intel.
> 
> Specifically, I am using
>   /share/apps/mvapich/intel/bin/mpicxx ,
> and the cluster set-up currently only uses static libraries, so I have
> used the --disable-shared flag when running configure for libmesh:
>   ./configure --prefix=${HOME}/gmxLocal --enable-threads
> --enable-float=no --enable-sse2 --enable-shared
> 
> I changed the configure.in file to choose icc as the C++ compiler, so I
> believe everything is consistent.
>   autoconf configure.in > configure2
>   ./configure2 --enable-everything --enable-second --disable-perflog
> --disable-bzip2 --disable-vsmoother --disable-shared
> 
> During the compilation of partitioner_factory.C I get no warnings, but
> the compilation suddenly dies:
> 
> bkraczek@prism2 ~/libmesh/ [1022] make
> Compiling C++ (in debug mode) src/partitioning/partitioner_factory.C...
> mpicxx -DDEBUG -Kc++eh -Krtti -O1 -w1 -g -wd504 -wd1572
> -I/home/bkraczek/libmesh/include/base
> -I/home/bkraczek/libmesh/include/enums
> -I/home/bkraczek/libmesh/include/error_estimation
> -I/home/bkraczek/libmesh/include/fe
> -I/home/bkraczek/libmesh/include/geom
> -I/home/bkraczek/libmesh/include/mesh
> -I/home/bkraczek/libmesh/include/numerics
> -I/home/bkraczek/libmesh/include/parallel
> -I/home/bkraczek/libmesh/include/partitioning
> -I/home/bkraczek/libmesh/include/quadrature
> -I/home/bkraczek/libmesh/include/solvers
> -I/home/bkraczek/libmesh/include/utils
> -I/home/bkraczek/libmesh/contrib/boost
> -I/home/bkraczek/libmesh/contrib/laspack
> -I/home/bkraczek/libmesh/contrib/parmetis/Lib
> -I/home/bkraczek/libmesh/contrib/metis/Lib
> -I/home/bkraczek/libmesh/contrib/sfcurves
> -I/home/bkraczek/libmesh/contrib/gzstream
> -I/home/bkraczek/libmesh/contrib/tecplot/include
> -I/home/bkraczek/libmesh/contrib/gmv
> -I/home/bkraczek/libmesh/contrib/tetgen
> -I/home/bkraczek/libmesh/contrib/triangle
> -I/home/bkraczek/libmesh/contrib/exodusii/Lib/include
> -I/home/bkraczek/libmesh/contrib/netcdf/Lib
> -I/home/bkraczek/libmesh/contrib/nemesis/Lib
> -I/home/bkraczek/libmesh/contrib/libHilbert/include
> -I/share/apps/petsc/2.3.3/include
> -I/share/apps/petsc/2.3.3/bmake/linux-gnu-c-debug
> -I/share/apps/petsc/2.3.3/linux-gnu-c-debug/include
> -I/share/apps/mvapich/intel/bin/include -c
> src/partitioning/partitioner_factory.C -o
> src/partitioning/partitioner_factory.x86_64-unknown-linux-gnu.dbg.o
> (0): internal error: backend signals
> 
> compilation aborted for src/partitioning/partitioner_factory.C (code 4)
> make: ***
> [src/partitioning/partitioner_factory.x86_64-unknown-linux-gnu.dbg.o]
> Error 4
> 
> So have you seen this before or should I bug Intel about it?
> 
> -Brent
> 
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Libmesh-users mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libmesh-users