Intel® C++ Compiler
Support and discussions for creating C++ code that runs on platforms based on Intel® processors.
Announcements
This community is designed for sharing of public information. Please do not share Intel or third-party confidential information here.
7677 Discussions

trouble building fftw3.2.2 with new compilers

Hans_J_
Beginner
146 Views
Hi All,
I've posted this in the Fortran forum, but as the main compiler used is C I'm doing the same here.
I am running OS 10.6.5 on an early 2008 Mac Pro, with the recent Xcode 3.2.4.
I just installed the new version 12.0 compilers, C++ and Fortran. To set them up I use
source /opt/intel/composerxe/bin/compilervars.sh intel64
then untarred fftw3.2.2.tar and ran
./configure CC=icc F77=ifort --with-our-malloc16 --enable-openmp --enable-sse2
Then I do
make check
Lots of things happen, but it then craps out, ending with
Executing "/Users/johnston/Numerical_Packages/fftw-3.2.2/tests/bench --verbose=1 --verify '//obc10x13x5x10v2' --verify '//ibc10x13x5x10v2' --verify '//ofc10x13x5x10v2' --verify '//ifc10x13x5x10v2' --verify 'obc10x13x5x10v2' --verify 'ibc10x13x5x10v2' --verify 'ofc10x13x5x10v2' --verify 'ifc10x13x5x10v2' --verify 'ok13bx9e11*8' --verify 'ik13bx9e11*8' --verify 'obr33x22v12' --verify 'ibr33x22v12' --verify 'ofr33x22v12' --verify 'ifr33x22v12' --verify '//obc33x22v12' --verify '//ibc33x22v12' --verify '//ofc33x22v12' --verify '//ifc33x22v12' --verify 'obc33x22v12' --verify 'ibc33x22v12' --verify 'ofc33x22v12' --verify 'ifc33x22v12' --verify 'ok120e01*168' --verify 'ik120e01*168' --verify 'obr8x5x2x13*8' --verify 'ibr8x5x2x13*8' --verify 'ofr8x5x2x13*8' --verify 'ifr8x5x2x13*8' --verify '//obc8x5x2x13*8' --verify '//ibc8x5x2x13*8' --verify '//ofc8x5x2x13*8' --verify '//ifc8x5x2x13*8' --verify 'obc8x5x2x13*8' --verify 'ibc8x5x2x13*8' --verify 'ofc8x5x2x13*8' --verify 'ifc8x5x2x13*8' --verify 'ok4o00v25' --verify 'ik4o00v25' --verify '//obr5x2x3x3' --verify '//ofr5x2x3x3' --verify 'obr5x2x3x3' --verify 'ibr5x2x3x3' --verify 'ofr5x2x3x3' --verify 'ifr5x2x3x3'"//obc10x13x5x10v2 4.78188e-16 2.18127e-15 7.68733e-16//ibc10x13x5x10v2 4.33957e-16 2.18127e-15 8.49837e-16//ofc10x13x5x10v2 4.00962e-16 2.04907e-15 8.27465e-16//ifc10x13x5x10v2 3.72694e-16 2.18127e-15 8.52547e-16FAILED /Users/johnston/Numerical_Packages/fftw-3.2.2/tests/bench: --verify '//obc10x13x5x10v2' --verify '//ibc10x13x5x10v2' --verify '//ofc10x13x5x10v2' --verify '//ifc10x13x5x10v2' --verify 'obc10x13x5x10v2' --verify 'ibc10x13x5x10v2' --verify 'ofc10x13x5x10v2' --verify 'ifc10x13x5x10v2' --verify 'ok13bx9e11*8' --verify 'ik13bx9e11*8' --verify 'obr33x22v12' --verify 'ibr33x22v12' --verify 'ofr33x22v12' --verify 'ifr33x22v12' --verify '//obc33x22v12' --verify '//ibc33x22v12' --verify '//ofc33x22v12' --verify '//ifc33x22v12' --verify 'obc33x22v12' --verify 'ibc33x22v12' --verify 'ofc33x22v12' --verify 'ifc33x22v12' --verify 'ok120e01*168' --verify 'ik120e01*168' --verify 'obr8x5x2x13*8' --verify 'ibr8x5x2x13*8' --verify 'ofr8x5x2x13*8' --verify 'ifr8x5x2x13*8' --verify '//obc8x5x2x13*8' --verify '//ibc8x5x2x13*8' --verify '//ofc8x5x2x13*8' --verify '//ifc8x5x2x13*8' --verify 'obc8x5x2x13*8' --verify 'ibc8x5x2x13*8' --verify 'ofc8x5x2x13*8' --verify 'ifc8x5x2x13*8' --verify 'ok4o00v25' --verify 'ik4o00v25' --verify '//obr5x2x3x3' --verify '//ofr5x2x3x3' --verify 'obr5x2x3x3' --verify 'ibr5x2x3x3' --verify 'ofr5x2x3x3' --verify 'ifr5x2x3x3'received signal 8make[2]: *** [check-local] Error 1make[1]: *** [check-am] Error 2make: *** [check-recursive] Error 1boussinesq:fftw-3.2.2 johnston$
I went back and tried the build with the 11.1.089 versions of the compilers, AND ALL GOES WELL.
This package should build without any problems, so I suspect some problem with the new compilers.
Could someone on the Intel side try this to see if you get the same problem?
Thanks, Hans
0 Kudos
2 Replies
Andreas_Klaedtke
Beginner
146 Views
Hi,

Not sure if this helps? I have just tested building the same version of fftw 3.2.2 on a Debian Linux system running in 32 bit mode, using the Intel 12.0.0 C/C++ compiler. The tests completed fine.
Hans_J_
Beginner
146 Views
thanks,
indeed, I found that the package built by configuring the compilers with ia32 ... but it should also work
using intel64 ...
Reply