stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Lemings" <Eric.Lemi...@roguewave.com>
Subject RE: [jira] Commented: (STDCXX-974) [EDG eccp/Linux] errors with optimization on long long in <pthreadtypes.h>
Date Wed, 23 Jul 2008 16:17:17 GMT
 

> -----Original Message-----
> From: Andrew Black [mailto:ablack@roguewave.com] 
> Sent: Wednesday, July 23, 2008 9:53 AM
> To: dev@stdcxx.apache.org
> Subject: Re: [jira] Commented: (STDCXX-974) [EDG eccp/Linux] 
> errors with optimization on long long in <pthreadtypes.h>
> 
> Eric Lemings wrote:
> [snip]
> >> Brad, they're all in //rwtest/..., the same place they were 
> >> the last time you had to make changes to the test driver. :)
> >>
> >>> [EDG eccp/Linux] errors with optimization on long long in 
> >> <pthreadtypes.h>
> > ...
> > 
> > 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...
> 
> 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.

Mime
View raw message