Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [jira] Commented: (STDCXX-974) [EDG eccp/Linux] errors with
 optimization on long long in <pthreadtypes.h>
Date: Wed, 23 Jul 2008 10:17:17 -0600
Message-ID: 
 <CFFDD219128FD94FB4F92B99F52D0A4901DB0689@exchmail01.Blue.Roguewave.Com>
Thread-Topic: [jira] Commented: (STDCXX-974) [EDG eccp/Linux] errors with
 optimization on long long in <pthreadtypes.h>
Thread-Index: Acjs3bDtFBU6GyYWRYuFO9SbK1y4mQAAYuWQ
References: <1149436000.1216765891939.JavaMail.jira@brutus>
 <CFFDD219128FD94FB4F92B99F52D0A4901DB0687@exchmail01.Blue.Roguewave.Com>
 <488753EB.3070000@roguewave.com>
From: "Eric Lemings" <Eric.Lemings@roguewave.com>
To: <dev@stdcxx.apache.org>

=20

> -----Original Message-----
> From: Andrew Black [mailto:ablack@roguewave.com]=20
> Sent: Wednesday, July 23, 2008 9:53 AM
> To: dev@stdcxx.apache.org
> Subject: Re: [jira] Commented: (STDCXX-974) [EDG eccp/Linux]=20
> errors with optimization on long long in <pthreadtypes.h>
>=20
> Eric Lemings wrote:
> [snip]
> >> Brad, they're all in //rwtest/..., the same place they were=20
> >> the last time you had to make changes to the test driver. :)
> >>
> >>> [EDG eccp/Linux] errors with optimization on long long in=20
> >> <pthreadtypes.h>
> > ...
> >=20
> > Well that explains it.  What are files from SourcePro's RWTest doing
> > STDCXX builds?  Is it supposed to pull RWTest files from 3 different
> > repositories, 1 in Subversion and 2 in Perforce?  If so, can't we
> > simplify this somehow?  Sheesh...
>=20
> The RWTest files from //rwtest/... are there because the legacy test
> suite (from //stdcxx/trunk/tests/...) depend on them.  Once porting of
> the test suite is complete, the dependencies on perforce will go away.

Right.  And the legacy tests are in the //stdcxx/trunk/tests
reposititory.
Is there any reason why the files could not reside in the
//stdcxx/trunk/tests/src directory (where one would expect to find
them)?
:)

As it is, if I were to update those files that would affect SourcePro,
wouldn't it?

Brad.