From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13489 invoked by alias); 26 Nov 2002 15:41:32 -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 13400 invoked from network); 26 Nov 2002 15:40:50 -0000 Received: from unknown (HELO fw-cam.cambridge.arm.com) (193.131.176.3) by sources.redhat.com with SMTP; 26 Nov 2002 15:40:50 -0000 Received: by fw-cam.cambridge.arm.com; id PAA05669; Tue, 26 Nov 2002 15:40:44 GMT Received: from unknown(172.16.1.2) by fw-cam.cambridge.arm.com via smap (V5.5) id xma005180; Tue, 26 Nov 02 15:40:10 GMT Received: from pc960.cambridge.arm.com (pc960.cambridge.arm.com [10.1.205.4]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id PAA14343; Tue, 26 Nov 2002 15:40:10 GMT Received: from pc960.cambridge.arm.com (rearnsha@localhost) by pc960.cambridge.arm.com (8.11.6/8.9.3) with ESMTP id gAQFe9p23798; Tue, 26 Nov 2002 15:40:09 GMT Message-Id: <200211261540.gAQFe9p23798@pc960.cambridge.arm.com> X-Authentication-Warning: pc960.cambridge.arm.com: rearnsha owned process doing -bs To: Andrew Cagney cc: Richard Earnshaw , gdb-patches@sources.redhat.com Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. Subject: Re: revamped gdb_mbuild.sh In-reply-to: Your message of "Tue, 26 Nov 2002 10:11:01 EST." <3DE38F05.6090803@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 Nov 2002 07:41:00 -0000 From: Richard Earnshaw X-SW-Source: 2002-11/txt/msg00648.txt.bz2 > > Richard, > >> > >> Finally got to trying the gdb_mbuild.sh script and, in the process, > >> integrated some, er, `new features' from my old local script: > >> > > > > > > Looks pretty good to me. My only comment is that we loose the ability to > > run gnumake with -j replacing it with simultaneous configures/builds > > of different targets. That means a higher transient disk usage (storage) > > which would be a marginal problem for me due to lack of disk quota on the > > multi-way machines... ;-( But that's me thinking about my environment, so > > it isn't a major objection > > I was wondering about a schema where one resource was allocated to > configure while the remaining N-1 were allocated to a single build. > That would mean an even faster turnaround on the first build (which I've > found is what I'm after :-). > > I guess we just wonder ... > > Andrew > > How about -c -j ? Ie x configures in parallel & y make jobs in parallel? R.