I've confirmed with Luca that this is not limited to my box, so I'm opening a bug because icc for me is just unusable this way.
The attached testcase produces this output:
flame@yamato mytmpfs % icc test-icc.c
/usr/include/limits.h(125): catastrophic error: could not open source file "limits.h"
# include_next <limits.h>
compilation aborted for test-icc.c (code 4)
the next limits.h that it should find is probably linux/limits.h (standing to what gcc -E produces), and indeed if I add -I/usr/include/linux to the command line it seems to work just fine.
For what might help, I'm running ~amd64 with these packages:
If you have any idea how we can get to solve this, I'd be very happy :)
Yes it seems it is a known bug:
However I don't have a proper solution yet.
Ok, I looked around in man and was able to run stuff by adding:
echo "-idirafter /usr/include/linux" >> /opt/intel/cc*/10.1*/bin/icpc.cfg
echo "-idirafter /usr/include/linux" >> /opt/intel/cc*/10.1*/bin/icc.cfg
I'm testing it now also on x86 and also checking if it breaks other compilations. Let me know if that works with the toolchains you have installed. thanks.
works for me
fixed in cvs.