stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Black <>
Subject Re: Build failure with ICC on windows
Date Tue, 10 Apr 2007 17:41:53 GMT
Greetings Farid.

Sorry about being a tad slow to get back to you on this patch.  I've
been busy with other things.

A problem that I am seeing with the resulting behavior is that the
build_icc-9.1.bat script is not being generated after this change was
committed, resulting in the attached (gziped) log.

Was this change intentional (in that users are expected to build using
the foo* family of solutiuons rather than the build_foo.bat scripts) or
unintentional?  If it was intentional, I believe the same behavior
change should be made for the msvc solution generation so that we are
consistent in our behavior.  If it was unintentional, I would find it
helpful to restore the generation of the script, as it is being used by
the nightly testing infrastructure.

--Andrew Black

Farid Zaripov wrote:
>> -----Original Message-----
>> From: Andrew Black [] 
>> Sent: Thursday, April 05, 2007 8:40 PM
>> To:
>> Subject: Build failure with ICC on windows
>> I am still observing failures with the ICL compiler on 
>> windows.  The failures are such that the config.h and 
>> config.log aren't available through the nightly testing 
>> system, so they don't appear in result page. 
>>   Attached is the run log of one of these runs.
>   As I see in the run log, the .configure project was built
> successfully,
> so config.h and config.log should be existing.
>> One element of concern to me is a line during the solution 
>> generation step:
>>> Converting solution to ICC.
>>> Conversion finished with code 2
>> Would it be possible to echo the output from running the 
>> conversion process (~line 176 of generate.wsf), so that it 
>> can be captured in the log file?
>   It's normal, because the intel conversion utility can't convert
> the projects of the 'utility' type (.configure and other which name
> is starting from '.'). Therefore the conversion utility returns 2 to
> report that not all projects was converted.
>> The second point of concern is just after the conversion step.
>>> -------
>>>   Build log was saved at 
>> "file://D:\bman5\builds\33400248\source-buildspace\build\icc-9
>> .1\15s\include\BuildLog.htm"
>>> .configure - 0 error(s), 0 warning(s)
>>> Compiling stdlib library...
>>> Compiling examples...
>>> Compiling rwtest library...
>>> Compiling tests...
>>> Compiling utils...
>>> Running examples...
>> With MSVC on the same platform, I see the output from the 
>> compile process after the line reading 'Compiling stdlib library...'
>> Any thoughts?
>   I've found the problem and I suppose that this patch should help:
> Farid.

View raw message