You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by Andrew Black <ab...@roguewave.com> on 2007/04/05 19:39:50 UTC
Build failure with ICC on windows
Greetings Farid, all.
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.
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?
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?
--Andrew Black
RE: Build failure with ICC on windows
Posted by Farid Zaripov <Fa...@epam.com>.
> -----Original Message-----
> From: Andrew Black [mailto:ablack@roguewave.com]
> Sent: Tuesday, April 10, 2007 8:42 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: Build failure with ICC on windows
>
> 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.
As I see, the build_icc-9.1.bat is not being generated due to
exception during running the script:
--------------
Writing solution on disk...
Converting solution icc-9.1.sln to ICC.
Conversion finished with code 2
Converting solution icc-9.1_ex.sln to ICC.
Conversion finished with code 2
Converting solution icc-9.1_tst.sln to ICC.
Conversion finished with code 2
Converting solution icc-9.1_loc.sln to ICC.
Conversion finished with code 2
Converting solution icc-9.1_tstloc.sln to ICC.
D:\bman5\builds\33408492\source-buildspace\etc\config\windows\generate.w
sf(89, 6) (null): The handle is invalid.
--------------
The exception thrown in line:
WScript.Echo(msg);
In the previous log (from
http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200704.mbo
x/%3c46153466.90202@roguewave.com%3e):
--------------
Converting solution to ICC.
Conversion finished with code 2
Generating build.bat...
D:\bman5\builds\33400248\source-buildspace\etc\config\windows\generate.w
sf(196, 6) (null): The handle is invalid.
--------------
The exception thrown in line:
WScript.Echo("Solution was generated successfully. See " +
resLogPath + " for details.");
That is strange error because of the previous calls WScript.Echo()
were successful.
I've asked the Google and found the one similar problem with
WScript.Echo(), but there has no answer:
http://groups.google.com.ua/group/microsoft.public.scripting.jscript/bro
wse_thread/thread/7d0eb00d02e97a13/2d6d1e8ce8fade40?lnk=st&q=WScript.Ech
o+The+handle+is+invalid.&rnum=8&hl=ru#2d6d1e8ce8fade40
I cannot reproduce that error. I can add try/catch, to hide this
exception, but it's just workaround...
For the beginning let's try to replace WScript.Echo() with
WScript.StdOut.WriteLine():
http://svn.apache.org/viewvc?view=rev&rev=527435
Farid.
Re: Build failure with ICC on windows
Posted by Andrew Black <ab...@roguewave.com>.
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 [mailto:ablack@roguewave.com]
>> Sent: Thursday, April 05, 2007 8:40 PM
>> To: stdcxx-dev@incubator.apache.org
>> 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:
> http://svn.apache.org/viewvc?view=rev&rev=525939
>
> Farid.
RE: Build failure with ICC on windows
Posted by Farid Zaripov <Fa...@epam.com>.
> -----Original Message-----
> From: Andrew Black [mailto:ablack@roguewave.com]
> Sent: Thursday, April 05, 2007 8:40 PM
> To: stdcxx-dev@incubator.apache.org
> 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:
http://svn.apache.org/viewvc?view=rev&rev=525939
Farid.