I know the '/v' is not a valid compiler option, but when I try to use it, I got the following error messages:
Intel(R) C++ Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 220.127.116.11 Build 20130607
Copyright (C) 1985-2013 Intel Corporation. All rights reserved.
icl: command line warning #10006: ignoring unknown option '/v'
icl: internal error: Assertion failed (shared/driver/driver.c, line 370)
Windows 7 64 bit Home Premium
Intel i5-2400 CPU
Thanks for reporting this issue!
I checked with 13.0 update5, it does have this issue. But with the 14.0 beta update it works fine. We will be only fixing high bugs for 13.x now, so I will not file any ticket for this one against 13.x.
Under a Linux-like environment for Windows, most of program need the usual configure, make, make install to get it running. Using Intel(R) C++ Intel(R) 64 Compiler XE 2013 under cygwin, I am trying to compile a program by first doing
I got the following error message : checking whether the C compiler works ... no
configure: error: C compiler cannot create executables
See 'config.log' for more details
Of course, looking at config.log, the error message is the same as Steven T.:
icl: command line warning #10006: ignoring unknown option '/-version'
icl: internal error: Assertion failed <shared/driver/driver.c, line 370>
So although it is a minor error, I cannot compile some programs that need to check the version of my C compiler during the configure process. Is there a simple way to fix this problem instead of waiting the 14.0 version ?
This is the test case the autoconf tools use for "checking for C compiler version" :
Where $CC is the compiler command (e.g. icc, icl, gcc) and in Stephane's case on windows it is using /-version rather than --version.
This is the test case the autoconf tools use for the "checking whether the C compiler works"
As per the OP, the testcase that is causing Stephane's autoconf to fail is likely the invocation of "icl /-version", which is your minimal reproducer testcase.
Try compiling the testcase in my post a few posts above yours (the same one Sergey quoted) or a simple hello-world. Post your icl command line and the output of the compilation.
This might be a longshot and I'm not too familiar with cygwin. Configure is likely using a temp directory to compile its tests (e.g /tmp on linux), and you may either not have that setup or may not have write permissions to it. Again, that might be a longshot but its worth looking at.