Re: 4.2.0 merge today

2007-06-28 Thread Martin Sebor

Farid Zaripov wrote:

-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 26, 2007 8:04 PM

To: stdcxx-dev@incubator.apache.org
Subject: 4.2.0 merge today

The one problematic platform that might need some attention 
is Intel Intel C++ 9.1 on Windows 2000/x86. A 12d build fails 
with this error:


Linking...(Intel C++ Environment)
xilink: executing 'link'
Creating library
D:\bman5\builds\33762791\source-buildspace\build\icc-9.1\12d\l
ib\libstd12d.lib
and object
D:\bman5\builds\33762791\source-buildspace\build\icc-9.1\12d\l
ib\libstd12d.exp
wctype.obj : fatal error LNK1103: debugging information 
corrupt; recompile module


Here's the log:

http://people.apache.org/~sebor/stdcxx/results/Windows_2000-ic
l-32b-9.1-12d-win32-log.gz.txt

Farid, can you reproduce this in your environment?


  The problem not reproduced at my workstation.


That's not good. We need to keep an eye on it.

Andrew, the Intel C++ builds on Windows 2000 are all in WAIT state
since 8PM last night. If they're still are no results can you please
see what's going on?

Thanks
Martin


RE: 4.2.0 merge today

2007-06-27 Thread Farid Zaripov
> -Original Message-
> From: Martin Sebor [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, June 26, 2007 8:04 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: 4.2.0 merge today
> 
> The one problematic platform that might need some attention 
> is Intel Intel C++ 9.1 on Windows 2000/x86. A 12d build fails 
> with this error:
> 
> Linking...(Intel C++ Environment)
> xilink: executing 'link'
> Creating library
> D:\bman5\builds\33762791\source-buildspace\build\icc-9.1\12d\l
> ib\libstd12d.lib
> and object
> D:\bman5\builds\33762791\source-buildspace\build\icc-9.1\12d\l
> ib\libstd12d.exp
> wctype.obj : fatal error LNK1103: debugging information 
> corrupt; recompile module
> 
> Here's the log:
> 
> http://people.apache.org/~sebor/stdcxx/results/Windows_2000-ic
> l-32b-9.1-12d-win32-log.gz.txt
> 
> Farid, can you reproduce this in your environment?

  The problem not reproduced at my workstation.

Farid.