as a follow-up to my issues with using ICC with GCC 4.9, I now compiled GCC 4.8. How do I now tell ICC to use that? I've tried the -cxxlib=/path/to/gcc-48 switch. But what does it really expect the path to contain? Apparently a bin/g++, OK. But now I get this:
icpc: error #10001: could not find directory in which the set of libstdc++ include files resides
What does this mean? The last lines of output from a strace -f run is pasted below. Note how it finds e.g. /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.2/include but then tries to access /usr/include/g++ - why?
it seems like the ICC does not use the environment variable GMON_OUT_PREFIX. Is tehre another way to change the filename of the gmon.out file?!
I'm learning TBB, according to TBB's getting started guide, I compile the TBB example in /opt/intel/tbb/examples/GettingStarted/sub_string_finder
compile with icc -O2 -DNDEBUG -o sub_string_finder_extended sub_string_finder_extended.cpp -ltbb -lrt：
Done building string.
Done with serial version.
Done with parallel version.
Done validating results.
Serial version ran in 4.51256 seconds
Parallel version ran in 1.27341 seconds
while trying to compile following code using "icc compiler 15.0.0", I am getting this error
I'm trying to build boost.Python with composer xe 2013 sp1:
boost version: 1_55
./bootstrap.sh --with-toolset=intel-darwin --with-libraries=python
./b2 variant=release threading=multi link=shared
In file included from ./boost/unordered_set.hpp(16),
I encounter a problem while compiling from command line using the Intel 64 Visual Studio 2012 prompt (Windows 7 64 bit). I do see that lib.exe is in the path before I run make. I get the the following error during compilation:
xilib.exe /verbose /nologo /OUT:lib/Windows64_x86_64_61_INTEL1312190_Release/RaX.lib obj/Windows64_x86_64_61_INTEL1312190_Release/AIProperty.obj obj
xilib: executing 'lib'
xilib: error #10036: unable to run 'lib'
I've recently upgraded to a newer version of the Intel Compiler (from 22.214.171.1240 to the latest - 126.96.36.199) and I seem to have a bunch of LINK2005 errors that I never had before - partial snippet below: