At 11:05 AM 1/17/2003, David Abrahams wrote:
>Toon Knapen <[EMAIL PROTECTED]> writes:
>
>> On Friday 17 January 2003 12:32, John Maddock wrote:
>>> So only the gcc tests will be run, I assume that you have some
detritus
>in
>>> bin directory from previous HP aCC runs, which is why you are seeing
>
On Friday 17 January 2003 11:28, Rene Rivera wrote:
> [2003-01-17] Toon Knapen wrote:
> >On Friday 17 January 2003 12:32, John Maddock wrote:
> >> So only the gcc tests will be run, I assume that you have some detritus
>
> in
>
> >> bin directory from previous HP aCC runs, which is why you are seei
[2003-01-17] Toon Knapen wrote:
>On Friday 17 January 2003 12:32, John Maddock wrote:
>> So only the gcc tests will be run, I assume that you have some detritus
in
>> bin directory from previous HP aCC runs, which is why you are seeing some
>> results listed. Add the necessary toolset(s) to test_
Toon Knapen <[EMAIL PROTECTED]> writes:
> On Friday 17 January 2003 12:32, John Maddock wrote:
>> So only the gcc tests will be run, I assume that you have some detritus in
>> bin directory from previous HP aCC runs, which is why you are seeing some
>> results listed. Add the necessary toolset(s)
Toon Knapen <[EMAIL PROTECTED]> writes:
> On Friday 17 January 2003 12:32, John Maddock wrote:
>> So only the gcc tests will be run, I assume that you have some detritus in
>> bin directory from previous HP aCC runs, which is why you are seeing some
>> results listed. Add the necessary toolset(s)
On Friday 17 January 2003 12:32, John Maddock wrote:
> So only the gcc tests will be run, I assume that you have some detritus in
> bin directory from previous HP aCC runs, which is why you are seeing some
> results listed. Add the necessary toolset(s) to test_tools.
Thanks John. Had some other m
