On 30/06/07, Andy Lester <[EMAIL PROTECTED]> wrote:
>
> perl Configure.pl --cc=icc --link=icc --ld=icc
> --ccflags=-I/opt/intel/compiler91/include/

Even with this, I get complaints that:

   icc: error #10001: could not find directory in which the set of
libstdc++ include files resides

I've apparently got a libstdc++-devel package installed at /usr/
include/c++/4.1.1/, but ICC is apparently not finding it.

Suggestions?



ICC='/opt/intel/cce/10.0.023'
CC="$ICC/bin/icc -gcc-name=/usr/local/bin/gcc -gcc-version=420"
CX="$CC"

# Make ICC see its own headers
CCFLAGS="-I$ICC/include -I/usr/include/c++/4.1.1"
# Turn off certain warnings
CCFLAGS="$CCFLAGS -wd810"   # conversion from "x" to "y" may lose
significant bits
CCFLAGS="$CCFLAGS -wd981"   # operands evaluated in unspecified order
CCFLAGS="$CCFLAGS -wd279"   # controlling expression is constant
CCFLAGS="$CCFLAGS -wd1419"  # external declaration in primary source
file
CCFLAGS="$CCFLAGS -wd1418"  # external definition with no prior
declaration
CCFLAGS="$CCFLAGS -wd1684"  # conversion from pointer to same-sized
integral type (potential portability problem)
CCWARN="-Wall"

perl Configure.pl \
     --cc="$CC" \
     --cxx="$CX" \
     --link="$CX" \
     --ld="$CX" \
     --ccflags="$CCFLAGS" \
     --ccwarn="$CCWARN" \


After having a look here at how you're setting things to pass to
Configure.pl, I realised that you might not be passing in the ccflags
you think you are.  When I was having a look at
tools/dev/parrot_coverage.pl I noticed that Configure.pl only seemed
to be taking the first option passed to --ccflags and nothing else.
It's therefore possible that your -I/usr/include/c++/4.1.1 isn't
actually making it into parrot's configuration data and therefore
never being passed to the C compiler, hence causing the problem you're
seeing.

Paul

Reply via email to