configure does not like icc |
 Issue
Number |
156845Â |
 Issue
Status |
Answered |
 Originator |
David Mathog |
 Submit
Date |
10/8/2002Â |
 Company |
Caltech |
 Last
Update |
10/29/2002 |
 Intel
Contact |
  |
 Closed Date |
10/29/2002 |
 Product
Type |
Development Environment (tools,SDV,EAP)Â |
 Product
Status |
Released |
 Product
Name |
Intel(R) C++ Compiler for Linux*Â |
Additional
product info --
 Â
Product Info Â
File Downloads (6) |
Question |
The autoconf "configure" script seems to be unable to run with icc. In particular, this was the configure for povray 3.5 source, downloaded from www.povray.org. Since at least half the software I use comes with ./configure this prevents simple builds of a lot of common software with ICC. The only "solution" I see now is to run configure and then manually change all of the (often many) makefiles by hand.
Example, obtain this source file and unpack:
ftp://ftp.povray.org/pub/povray/Official/Linux/povuni_s.tgz
Drop into the top level and try to make:
./configure
work. I tried all sorts of combinations of shell definitions for CC,CXX,CFLAGS,LFLAGS,CXXFLAGS and in no case would it get past both the compiler and preprocessor checks.
The farthest was with:
export CC=/usr/common/intelcompilers/compiler60/ia32/bin/icc export CPP=$CC export CXX=$CC export CFLAGS="-O3 -axK -ipo" export CXXFLAGS=$CFLAGS export LFLAGS="-L/usr/common/intelcompilers/compiler60/lib" ./configure
which choked at the preprocessor level:
checking whether /usr/common/intelcompilers/compiler60/ia32/bin/icc accepts -g... yes checking how to run the C preprocessor... /usr/common/intelcompilers/compiler60/ia32/bin/icc configure: error: C preprocessor "/usr/common/intelcompilers/compiler60/ia32/bin/icc" fails sanity check
Thanks. Please also email reply to address@hidden |
|
Updated by Intel: 10/29/2002 1:24:18 PM |
David,
I will close this now since I believe my suggestion fixed your problem. You may reopen if you have further questions.
Thank you, Micah |
Updated by Intel: 10/17/2002 1:13:27 PM |
David,
Do you have any further questions on this?
--Micah |
Updated by Intel: 10/15/2002 12:53:27 PM |
David,
I
am able to reproduce your claims as stated. I believe there is not an issue
here, though. I find that when I omit the definition of `CPP' the script
runs successfully. It is fine whether I say:
$ export CC=icc $ export CXX=$CC $ export CFLAGS="-O3 -axK -ipo" $ export CXXFLAGS="-O3 -axK -ipo" $ ./configure # success!
OR
$ CC=icc CXX=$CC CFLAGS="-O3 -axK -ipo" CXXFLAGS="-O3 -axK -ipo" ./configure # success!
* * *
Now
autoconf can figure out to use `icc -E' instead of `icc'. Note that gcc/g++
fail in the same way when `CPP' is set. Keep in mind that I have `unset CPP',
which is necessary to make this work (if you have defined it).
BTW, I have already set appropriate env vars with iccvars.sh, so no need for absolute paths in CC, CXX, etc.
Please confirm that you are able to get this working.
Thank you, Micah |
Feedback from David Mathog: 10/8/2002 12:19:59 PM |
The configure file for POVRAY does not seem to have -cc, -cflags etc. switches, but it does look at the environmental variables first thing and use those values. So by using the export statements before configure (as shown in the initial report) I effectively did the same thing as the command line switches in mpich.
With the difference that it didn't work for POVRAY.
For what it's worth the configure file for this package was made by autoconf 2.52. Probably the best solution is to submit to the gnu folks the right changes to autoconf so that future versions know enough about icc/ifc etc. to work properly.
Thanks. |
Updated by Intel: 10/8/2002 11:44:07 AM |
David,
I have received your configure issue. What I have seen work for other projects is something like the following:
"The
current version of MPICH (version 1.2.3) supports the Intel compilers. Here's
the configure command that I use during installation:
./configure -fc=ifc -f90=ifc -cc=icc -prefix=/usr/local/mpich-1.2.3
If
you check the output from the configure command you'll see that MPICH runs
a series of tests on the Intel compilers and adds the appropriate Intel-specific
options."
Give this a try and let me know if you are successful.
Thank you, Micah Intel Compiler Support |
Customer Impact:
|
Showstopper
| Edit |
Request Type:
|
Problem Report
| Edit |
Package ID (run icid):
|
C++ Support Package ID : l_cc_p_6.0.1.304-ACAD
| Edit |
Component:
|
Intel Compiler for 32-bit apps
| Edit |
Build/Development Platform:
|
IA-32 Host
| Edit |
Linux* Operating System:
|
Other (specify below)
| Edit |
Other Linux* OS (not listed above):
|
RH 7.3
| Edit |
glibc version:
|
2.2.5-39
| |
Kernel version:
|
2.4.18-10smp
| Edit |
|
|
 Date Posted |
 Files
Available from Intel Customer Support |
 Files Size (bytes) |
<<No
downloads available>> |
 Date Uploaded |
 Files
Uploaded to Intel Customer Support |
 Files Size (bytes) |
<<No
uploads found>> |