Greetings Faird
The reason the ICC builds on windows aren't showing up is part exporter
bug, part infrastructure bug. The exporter bug is the same bug that's
been plaguing all our catastrophic failures, where runs with missing
attachments aren't exported. The glue scripts rely on the generated
build_<compiler>.bat scripts. These scripts are generated for the MSVC
compiler, but not for the ICC compiler. Also note that the last few
lines of output from the call to generate.bat are as follows:
Converting solution icc-9.1_ex.sln to ICC.
D:\bman5\builds\33651394\source-buildspace\etc\config\windows\generate.wsf(90, 6) (null): The handle is invalid.
--Andrew Black
Farid Zaripov (JIRA) wrote:
[ https://issues.apache.org/jira/browse/STDCXX-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499088 ]
Farid Zaripov commented on STDCXX-188:
--------------------------------------
The warning is still there. But I don't see the results of the nightly builds
with Intel C++ / Windows.
We can either disable warning or put definition of the static const char
_C_name into #ifndef / #endif.
[Intel C++ 9.1/Windows] warning #177 in library builds
------------------------------------------------------
Key: STDCXX-188
URL: https://issues.apache.org/jira/browse/STDCXX-188
Project: C++ Standard Library
Issue Type: Bug
Components: Build
Affects Versions: 4.1.3
Environment: MS Windows 2000, Intel C++ 9.1.0.22 compiler
Reporter: Anton Pevtsov
Assigned To: Farid Zaripov
Priority: Trivial
Build log:
Compiling with Intel(R) C++ 9.1 ...(Intel C++ Environment)
...
typeinfo.cpp
C:\Projects\apache\src\.\typeinfo.cpp(91): warning #177: variable "_C_name" was
declared but never referenced
static const char _C_name[] = "";
^
...
