You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by Martin Sebor <se...@roguewave.com> on 2007/07/25 06:21:12 UTC
Intel C++ errors on Windows
Andrew, Farid,
Our Intel C++ builds (both 9.1 and 10) on Windows are failing with
various configuration errors. Have you guys seen them yet and if so,
do you have any comments on what's going on?
Here's one from this build:
http://people.apache.org/~sebor/stdcxx/results/win_2000-4-x86-icl-32b-9.1-11s-558871-log.gz.txt
Performing Custom Build Step
The system cannot find the path specified.
Configuring for icc-9.1 - 11s Debug Static
checking if compiler is sane... Configure: Fatal error: Compiler failed
sanity check
You may see log here:
file://D:/bman5/builds/33883718/source-buildspace/build/icc-9.1/11s/include/config.log
Project : error PRJ0019: A tool returned an error code from "Performing
Custom Build Step"
The config.log message indicates the compiler driver isn't installed:
Compiling with command "icl /c /EHsc /GS /D_CRT_SECURE_NO_DEPRECATE /GR
/MTd /Zi /Gm
/I"D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests"
/I"D:\bman5\builds\33883718\source-buildspace\include"
/Fo"D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests\\"
/Fd"D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests\sanity.pdb"
"D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests\sanity.cpp""
'icl' is not recognized as an internal or external command,
operable program or batch file.
Another but different one here:
http://people.apache.org/~sebor/stdcxx/results/win_2003-1-amd64-icl-32b-10.0-12d-win32-558871-log.gz.txt
### Creating solution
Solution generation script
Checking arguments...
Building directory tree created
Checking consistence...
conversion utility not found
### Building solution / Creating HTML log
'build\build_icc-10.0.bat' is not recognized as an internal or external
command,
Thanks
Martin
Re: Intel C++ errors on Windows
Posted by Martin Sebor <se...@roguewave.com>.
Andrew Black wrote:
> Greetings Martin
>
> I believe the failures are environment caused.
>
> For the Intel 10 builds on Windows 2003 AMD64, the Intel 10 compiler
> isn't installed (Though the 9.1 compiler appears to be).
>
> For the Intel 9 builds on Windows 2000 and Windows 2003, the cause is
> the use of an incorrect setenv.
Sounds like a job for IT. Did you let them know about it and if
so, what's the ETA on a fix? If it's not soon it might make sense
to remove these builds from the schedule until they are set up
correctly.
Martin
>
> --Andrew Black
>
> Martin Sebor wrote:
>> Andrew, Farid,
>>
>> Our Intel C++ builds (both 9.1 and 10) on Windows are failing with
>> various configuration errors. Have you guys seen them yet and if so,
>> do you have any comments on what's going on?
>>
>> Here's one from this build:
>> http://people.apache.org/~sebor/stdcxx/results/win_2000-4-x86-icl-32b-9.1-11s-558871-log.gz.txt
>>
>>
>> Performing Custom Build Step
>> The system cannot find the path specified.
>> Configuring for icc-9.1 - 11s Debug Static
>> checking if compiler is sane... Configure: Fatal error: Compiler failed
>> sanity check
>> You may see log here:
>> file://D:/bman5/builds/33883718/source-buildspace/build/icc-9.1/11s/include/config.log
>>
>> Project : error PRJ0019: A tool returned an error code from "Performing
>> Custom Build Step"
>>
>> The config.log message indicates the compiler driver isn't installed:
>> Compiling with command "icl /c /EHsc /GS /D_CRT_SECURE_NO_DEPRECATE /GR
>> /MTd /Zi /Gm
>> /I"D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests"
>> /I"D:\bman5\builds\33883718\source-buildspace\include"
>> /Fo"D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests\\"
>> /Fd"D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests\sanity.pdb"
>> "D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests\sanity.cpp""
>>
>> 'icl' is not recognized as an internal or external command,
>> operable program or batch file.
>>
>>
>> Another but different one here:
>> http://people.apache.org/~sebor/stdcxx/results/win_2003-1-amd64-icl-32b-10.0-12d-win32-558871-log.gz.txt
>>
>> ### Creating solution
>> Solution generation script
>> Checking arguments...
>> Building directory tree created
>> Checking consistence...
>> conversion utility not found
>> ### Building solution / Creating HTML log
>> 'build\build_icc-10.0.bat' is not recognized as an internal or external
>> command,
>>
>> Thanks
>> Martin
Re: Intel C++ errors on Windows
Posted by Andrew Black <ab...@roguewave.com>.
Greetings Martin
I believe the failures are environment caused.
For the Intel 10 builds on Windows 2003 AMD64, the Intel 10 compiler
isn't installed (Though the 9.1 compiler appears to be).
For the Intel 9 builds on Windows 2000 and Windows 2003, the cause is
the use of an incorrect setenv.
--Andrew Black
Martin Sebor wrote:
> Andrew, Farid,
>
> Our Intel C++ builds (both 9.1 and 10) on Windows are failing with
> various configuration errors. Have you guys seen them yet and if so,
> do you have any comments on what's going on?
>
> Here's one from this build:
> http://people.apache.org/~sebor/stdcxx/results/win_2000-4-x86-icl-32b-9.1-11s-558871-log.gz.txt
>
>
> Performing Custom Build Step
> The system cannot find the path specified.
> Configuring for icc-9.1 - 11s Debug Static
> checking if compiler is sane... Configure: Fatal error: Compiler failed
> sanity check
> You may see log here:
> file://D:/bman5/builds/33883718/source-buildspace/build/icc-9.1/11s/include/config.log
>
> Project : error PRJ0019: A tool returned an error code from "Performing
> Custom Build Step"
>
> The config.log message indicates the compiler driver isn't installed:
> Compiling with command "icl /c /EHsc /GS /D_CRT_SECURE_NO_DEPRECATE /GR
> /MTd /Zi /Gm
> /I"D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests"
> /I"D:\bman5\builds\33883718\source-buildspace\include"
> /Fo"D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests\\"
> /Fd"D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests\sanity.pdb"
> "D:\bman5\builds\33883718\source-buildspace\build\icc-9.1\11s\include\tests\sanity.cpp""
>
> 'icl' is not recognized as an internal or external command,
> operable program or batch file.
>
>
> Another but different one here:
> http://people.apache.org/~sebor/stdcxx/results/win_2003-1-amd64-icl-32b-10.0-12d-win32-558871-log.gz.txt
>
> ### Creating solution
> Solution generation script
> Checking arguments...
> Building directory tree created
> Checking consistence...
> conversion utility not found
> ### Building solution / Creating HTML log
> 'build\build_icc-10.0.bat' is not recognized as an internal or external
> command,
>
> Thanks
> Martin