From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23851 invoked by alias); 2 Dec 2002 16:18:09 -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 23829 invoked from network); 2 Dec 2002 16:18:01 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 2 Dec 2002 16:18:01 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18Iv9B-0003Bn-00; Mon, 02 Dec 2002 12:18:21 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18ItH5-0002wn-00; Mon, 02 Dec 2002 11:18:23 -0500 Date: Mon, 02 Dec 2002 08:18:00 -0000 From: Daniel Jacobowitz To: Nathanael Nerode Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com, binutils@sources.redhat.com, dj@redhat.com Subject: Re: (toplevel) introduce host subdir configuration in Makefile Message-ID: <20021202161822.GA11078@nevyn.them.org> Mail-Followup-To: Nathanael Nerode , gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com, binutils@sources.redhat.com, dj@redhat.com References: <20021128221312.GA20889@doctormoo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021128221312.GA20889@doctormoo> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-12/txt/msg00021.txt.bz2 On Thu, Nov 28, 2002 at 05:13:12PM -0500, Nathanael Nerode wrote: > This introduces configure targets for host modules, but doesn't use them > by default. To use them right now, you need to configure --norecursion > and then hit each one by hand. I'll make them used automatically once I > fiddle around and get the dependencies right for sure. > > At the moment it appears that 'gcc','zlib','fastjar', and 'libiberty' can > be configured in any order relative to each other (nice and straightforward). > If anyone knows of specific configure order dependencies, they should tell > me. I'll be spending a while fiddling with gcc and src trying to identify > any other real configure order dependencies. > > The 'safe' way to do it is to have all-foo for *every* host module foo > depend on configure-bar for *every* host module bar, and to have > a huge list of configure-configure dependencies forcing a specific order. > But that's stupid, and it looks to me like there are actually few if any > of these dependences. (Apart from all-foo: configure-foo). I did include > the one which was actually documented. > > Note that the configure target was written to replicate existing behavior > as closely as possible, and is therefore a bit squirrely; I'll deal with > that later, but at the moment I want to break as little as possible. You may already know this, but just to be careful I'll mention it anyway... it is not necessarily safe to configure more than one subdirectory at a time. One possibly gotcha is the updating of $cache_file. It isn't done atomically and so if you happen to have two subdirectories with the same (essentially) configure.in, and they happen to get started on an SMP system by make -j2 at (essentially) the same time, you can blow out the cache file. This isn't entirely hypothetical. A similar thing happened in libiberty with two invocations of config.status. Now, on the other hand, we could configure GCC while building libiberty. It would be nice to have a way to throw each configure step into its own log file so that they don't interleave on the screen, someday. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer