Interesting Jeff. The only thing this can mean is that ICC is failing the compiler test which we use to detect the faulty version of gcc.
I'll try an pull that test put and send it to you and we can try and figure out why. It might be tomorrow before I get a chance however as I am out this evening. Bill. On Monday, 22 October 2012, Jeff Gilchrist wrote: > On Sun, Oct 21, 2012 at 1:15 PM, Bill Hart > <[email protected]<javascript:;>> > wrote: > > > I have just uploaded alpha4 to our website http://mpir.org/ > > > > This will hopefully be the last alpha. It merely adds a patch to speed > > up the FFT slightly in certain instances. > > I found some issues with ICC. > > If I use mpir 2.5.1 with just a simple ./configure on this sytem, it > works fine with ICC version 12.1.3 (gcc version 4.4.6 compatibility). > If I try with MPIR 2.6.0 I get a could not find a working compiler > error. It is bailing out with "no, gcc-4.3.2 on 64bit is bad" error > even though I'm using ICC 12.1.3 (and the version of GCC installed on > the system is 4.4.6). Here is the output: > > checking build system type... k102-unknown-linux-gnu > checking host system type... k102-unknown-linux-gnu > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking ABI=64 > checking compiler icc -O2 -I/opt/sharcnet/mkl/10.3.9/mkl/include > -I/opt/sharcnet/openmpi/1.6.2/intel/include > -I/opt/sharcnet/openmpi/1.6.2/intel/lib > -I/opt/sharcnet/intel/12.1.3/icc/include > -I/opt/sharcnet/intel/12.1.3/icc/include/cilk > -I/opt/sharcnet/intel/12.1.3/ifc/include... no, gcc-4.3.2 on 64bit is > bad , try -O1 or -fno-strict-aliasing for the flags > checking ABI=32 > checking compiler icc -O2 -I/opt/sharcnet/mkl/10.3.9/mkl/include > -I/opt/sharcnet/openmpi/1.6.2/intel/include > -I/opt/sharcnet/openmpi/1.6.2/intel/lib > -I/opt/sharcnet/intel/12.1.3/icc/include > -I/opt/sharcnet/intel/12.1.3/icc/include/cilk > -I/opt/sharcnet/intel/12.1.3/ifc/include... no, gcc-4.3.2 on 64bit is > bad , try -O1 or -fno-strict-aliasing for the flags > configure: error: could not find a working compiler, see config.log for > details > > I'm getting the same error on both our Opteron and Intel system that > has the same version of the compiler on it. Those results are here: > > checking build system type... nehalem-unknown-linux-gnu > checking host system type... nehalem-unknown-linux-gnu > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking ABI=64 > checking compiler icc -O2 -I/opt/sharcnet/openmpi/1.6.2/intel/include > -I/opt/sharcnet/openmpi/1.6.2/intel/lib > -I/opt/sharcnet/mkl/10.3.9/mkl/include > -I/opt/sharcnet/intel/12.1.3/icc/include > -I/opt/sharcnet/intel/12.1.3/icc/include/cilk > -I/opt/sharcnet/intel/12.1.3/ifc/include... no, gcc-4.3.2 on 64bit is > bad , try -O1 or -fno-strict-aliasing for the flags > checking ABI=32 > checking compiler icc -O2 -I/opt/sharcnet/openmpi/1.6.2/intel/include > -I/opt/sharcnet/openmpi/1.6.2/intel/lib > -I/opt/sharcnet/mkl/10.3.9/mkl/include > -I/opt/sharcnet/intel/12.1.3/icc/include > -I/opt/sharcnet/intel/12.1.3/icc/include/cilk > -I/opt/sharcnet/intel/12.1.3/ifc/include... no, gcc-4.3.2 on 64bit is > bad , try -O1 or -fno-strict-aliasing for the flags > configure: error: could not find a working compiler, see config.log for > details > > Do you need any other info from config.log or want me to try anything > else? As I said, mpir 2.5.1 still works fine to do ./configure, make, > make check, so it is something that has changed in 2.6. > > Jeff. > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to [email protected]<javascript:;> > . > To unsubscribe from this group, send email to > [email protected] <javascript:;>. > For more options, visit this group at > http://groups.google.com/group/mpir-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
