Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of Farid_Zaripov@epam.com
 designates 217.21.63.3 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: svn commit: r586502 -
 /incubator/stdcxx/branches/4.2.0/include/rw/_config-msvcrt.h
Date: Fri, 19 Oct 2007 19:02:31 +0300
Message-ID: <7BDB2168BEAEF14C98F1901FD2DE64380117EC90@epmsa009.minsk.epam.com>
In-Reply-To: <4718D280.1070404@roguewave.com>
Thread-Topic: svn commit: r586502 -
 /incubator/stdcxx/branches/4.2.0/include/rw/_config-msvcrt.h
Thread-Index: AcgSaFuvas8RQCX0Sgau/L7uSJHx3AAAE4Yg
References: <20071019153011.85CD11A9832@eris.apache.org>
 <4718D280.1070404@roguewave.com>
From: "Farid Zaripov" <Farid_Zaripov@epam.com>
To: <stdcxx-dev@incubator.apache.org>

> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com]=20
> Sent: Friday, October 19, 2007 6:51 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: svn commit: r586502 -=20
> /incubator/stdcxx/branches/4.2.0/include/rw/_config-msvcrt.h
>=20
> I take it this is necessary for 4.2.0?

  Definitely. I've tested the 4.2.0 HEAD revision and got many
linker errors in static builds. The same results you can see
in nightly builds results. There all static builds are pink color.

http://people.apache.org/~sebor/stdcxx/results/

> (If so, we will have to create a new release candidate.)

  I think we can also include the following patch in 4.2.0 release:
http://www.nabble.com/__rw_once-warnings-in-non-reentrant-Windows-builds
--tf4634599.html#a13295746

Farid.