From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26878 invoked by alias); 27 Nov 2002 18:05:41 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 26811 invoked from network); 27 Nov 2002 18:05:39 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 27 Nov 2002 18:05:39 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id B79013F30; Wed, 27 Nov 2002 13:05:35 -0500 (EST) Message-ID: <3DE5096F.3080906@redhat.com> Date: Wed, 27 Nov 2002 10:05:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Richard.Earnshaw@arm.com Cc: gdb-patches@sources.redhat.com, Richard Earnshaw , David Carlton Subject: Re: revamped gdb_mbuild.sh References: <200211271750.gARHox401110@pc960.cambridge.arm.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-11/txt/msg00682.txt.bz2 > PS: Something I forgot to mention. >> >> The new script, once it has successfully configured, built, and run a >> target, replaces the BUILDDIR/TARGET directory with a BUILDDIR/TARGET >> file (-f removes this, this is how the script knows to not try to re-do >> a build). >> >> Anyway, the significant thing here is that the file contains the output >> from the TARGET's ``(gdb) maint print architecture'' command. Having >> that output for each architectures available [suddenly] makes it >> possible to examine/compare all the settings and, consequently, change >> those settings to something more logical. >> >> enjoy, >> Andrew >> > > > What happens to the build logs? Do we keep those? At present both build and config logs, and the build directory get removed. Only architecture output is left. I think this is ok since, unlike before, the command is restartable. If the build fails, just restart it with a more verbose option(1). ? Andrew (1) Although this doesn't help the mn10300's -j 2 build problem. The second run mysteriously worked.