From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14502 invoked by alias); 5 Dec 2002 22:29:51 -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 14439 invoked from network); 5 Dec 2002 22:29:49 -0000 Received: from unknown (HELO mta02ps.bigpond.com) (144.135.25.134) by sources.redhat.com with SMTP; 5 Dec 2002 22:29:49 -0000 Received: from bubble.local ([144.135.25.87]) by mta02ps.bigpond.com (Netscape Messaging Server 4.15 mta02ps Jul 16 2002 22:47:55) with SMTP id H6O3TM00.757 for ; Fri, 6 Dec 2002 08:29:46 +1000 Received: from CPE-144-136-184-243.sa.bigpond.net.au ([144.136.184.243]) by psmam07.mailsvc.email.bigpond.com(MailRouter V3.2a 125/2282405); 06 Dec 2002 08:29:46 Received: (qmail 19349 invoked by uid 179); 5 Dec 2002 22:29:45 -0000 Date: Thu, 05 Dec 2002 14:36:00 -0000 From: Alan Modra To: Zack Weinberg Cc: Nathanael Nerode , klee@apple.com, gdb-patches@sources.redhat.com, binutils@sources.redhat.com, newlib@sources.redhat.com, gcc@gcc.gnu.org Subject: Re: [RFC] Update to current automake/autoconf/libtool versions. Message-ID: <20021205222945.GX27956@bubble.sa.bigpond.net.au> Mail-Followup-To: Zack Weinberg , Nathanael Nerode , klee@apple.com, gdb-patches@sources.redhat.com, binutils@sources.redhat.com, newlib@sources.redhat.com, gcc@gcc.gnu.org References: <20021205190728.GA11507@doctormoo> <87hedsi247.fsf@egil.codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87hedsi247.fsf@egil.codesourcery.com> User-Agent: Mutt/1.4i X-SW-Source: 2002-12/txt/msg00193.txt.bz2 On Thu, Dec 05, 2002 at 01:31:52PM -0800, Zack Weinberg wrote: > But I do see a way forward. It goes like this. One directory at a > time, we go through and do whatever it takes to get that directory's > configure.in to work properly with both 2.13 and 2.5x, independent of > what version of autoconf was used to generate configure in other > directories. This may involve submitting patches to the autoconf > maintainers. Whoever volunteers to do this must be willing to > maintain these scripts in that state indefinitely -- I did it for the > gcc subdirectory a year or so ago and I discovered a couple weeks back > that it had mysteriously broken. I'm concerned that this proposal may be raising the bar too high. How long has it been since some poor fool^H^H^H^H^H^H^H^H^Hbrave soul attempted to modernize binutils configury? It seems that the major impact of configuring parts of a tree using different autoconf versions will be on people using --enable-maintainer-mode, so another solution might be to extend --enable-maintainer-mode to accept a list of directories. I suspect most developers will only want --enable-maintainer-mode in the particular area they work on. -- Alan Modra IBM OzLabs - Linux Technology Centre