[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Intel compiler and autoconf

From: David Mathog
Subject: Intel compiler and autoconf
Date: Wed, 30 Oct 2002 08:09:31 -0800

I had difficulty using the intel linux compiler (icc) with the
autoconf generated configure in the current POVRAY package. 
Thread 156845 on 


(account required) discusses this.  The Intel engineers feel
that this is a problem with autoconf and not their compiler.
They suggested I pass the issue on to you folks.

I've attached an HTML copy of this thread's web page.


David Mathog
Manager, Sequence Analysis Facility, Biology Division, Caltech
Intel Premier Support Homewww.intel.comdeveloper.intel.comGive us FeedbackLog Out
Intel Private Site
View New Updates  1
View Active Issues  0
 Premier Issue Management
 Submit Issues
 View Issues
 My Account
 My Reports
 Premier Features
 What's New
 File Downloads
 Premier Resources
 Premier Product Access
 My Profile/Products

To help ensure the best service, please complete this survey.
Did we answer your question for this issue?
On a scale of 1(low) to 5 (good), how do you rate the quality of support?
Please add your comments about this issue here.

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)
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:


Drop into the top level and try to make:


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 LFLAGS="-L/usr/common/intelcompilers/compiler60/lib"

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
  Issue Communication Add an Issue Update
Updated by Intel: 10/29/2002 1:24:18 PM

I will close this now since I believe my suggestion fixed your problem. You may reopen if you have further questions.

Thank you,
Updated by Intel: 10/17/2002 1:13:27 PM

Do you have any further questions on this?

Updated by Intel: 10/15/2002 12:53:27 PM

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!


$ 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,
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.

Updated by Intel: 10/8/2002 11:44:07 AM

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,
Intel Compiler Support
Issue Detail
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
  Files Associated to This Issue Attach File
 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>>

* Legal Information and Privacy Policy © 2002 Intel Corporation

reply via email to

[Prev in Thread] Current Thread [Next in Thread]