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)
Message-ID: <488753EB.3070000@roguewave.com>
Date: Wed, 23 Jul 2008 09:53:15 -0600
From: Andrew Black <ablack@roguewave.com>
User-Agent: Thunderbird 1.5.0.14 (X11/20060911)
MIME-Version: 1.0
To: dev@stdcxx.apache.org
Subject: Re: [jira] Commented: (STDCXX-974) [EDG eccp/Linux] errors with
 optimization
 on long long in <pthreadtypes.h>
References: <1149436000.1216765891939.JavaMail.jira@brutus>
 <CFFDD219128FD94FB4F92B99F52D0A4901DB0687@exchmail01.Blue.Roguewave.Com>
In-Reply-To: 
 <CFFDD219128FD94FB4F92B99F52D0A4901DB0687@exchmail01.Blue.Roguewave.Com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.

--Andrew Black

> 
> Brad.