From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32201 invoked by alias); 29 Nov 2002 16:44:38 -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 32169 invoked from network); 29 Nov 2002 16:44:37 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 29 Nov 2002 16:44:37 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 3CB5A3F30; Fri, 29 Nov 2002 11:44:31 -0500 (EST) Message-ID: <3DE7996F.4030801@redhat.com> Date: Fri, 29 Nov 2002 08:44: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: Nathanael Nerode Cc: gdb-patches@sources.redhat.com, dj@redhat.com Subject: Re: (toplevel) introduce host subdir configuration in Makefile References: <20021128221312.GA20889@doctormoo> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-11/txt/msg00742.txt.bz2 > 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. Nathanael, Some heads up. GDB requires an ISO C compiler and on some systems that involves running the compiler with specific flags (-Ae, I think, on HP/UX?). The problem is that GDB can't test/configure this directly. By time time it has a say in the matter, it is too late. The top level will need to do this very early on. While GDB has a depencency on the SIM directory, it resolves it by testing for ${srcdir)/../sim so that should be ok. While INSIGHT has a dependency on tcl/tk, it appears to resolve it doing some pretty agressive hunting. It looks in both ${srcdir} and `pwd`. Andrew