Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <45886ABF.7050801@roguewave.com>
Date: Tue, 19 Dec 2006 15:42:07 -0700
From: Andrew Black <ablack@roguewave.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.0.8) Gecko/20061029 SeaMonkey/1.0.6
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: ls output in Tru64 build logs
References: <45884739.7010907@roguewave.com>
In-Reply-To: <45884739.7010907@roguewave.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Greetings Martin.

The ls output does indeed come from the nightly testing glue script. 
The intent was to diagnose some issues which were leading to failed 
builds on seismic (the machine used for compaq-7.1 builds).  I don't 
think this cause has resurfaced recently, so I have removed the command.

--Andrew Black

Martin Sebor wrote:
> All our Tru64 build logs have a long list of recursive directory
> listings rooted at ${BUILDDIR}/.. near the top (see below). I
> suspect it comes from the script that invokes the top level
> makefile. Andrew, can you look into what's causing it when you
> have a moment and if it is something in your script get rid of
> it?
> 
> http://people.apache.org/~sebor/stdcxx/results/tru64_51-compaq-7.1-15d-log.gz.txt 
> 
> 
> Thanks
> Martin