From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2456 invoked by alias); 5 Dec 2002 19:08:25 -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 2430 invoked from network); 5 Dec 2002 19:08:23 -0000 Received: from unknown (HELO mailout5-0.nyroc.rr.com) (24.92.226.122) by sources.redhat.com with SMTP; 5 Dec 2002 19:08:23 -0000 Received: from doctormoo (syr-24-24-16-193.twcny.rr.com [24.24.16.193]) by mailout5-0.nyroc.rr.com (8.11.6/RoadRunner 1.20) with ESMTP id gB5J8GF05522; Thu, 5 Dec 2002 14:08:17 -0500 (EST) Received: from neroden by doctormoo with local (Exim 3.36 #1 (Debian)) id 18K1LM-0004ge-00; Thu, 05 Dec 2002 14:07:28 -0500 Date: Thu, 05 Dec 2002 11:08:00 -0000 To: klee@apple.com, gdb-patches@sources.redhat.com Cc: binutils@sources.redhat.com, newlib@sources.redhat.com, gcc@gcc.gnu.org Subject: Re: [RFC] Update to current automake/autoconf/libtool versions. Message-ID: <20021205190728.GA11507@doctormoo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i From: Nathanael Nerode X-SW-Source: 2002-12/txt/msg00164.txt.bz2 >1. Please make sure to coordinate with Nathanael Nerode, who is in the >middle of extensive autoconf-related work in the GCC repository. I really would like to see the tree using autoconf 2.5x as soon as possible; if this can be done before I autoconfiscate the top level (which is not autoconfiscated yet) it will save me an awful lot of trouble, since I can then use autoconf 2.5x for that autoconfiscation. :-/ Your patch as is updates bfd binutils gas gdb gprof ld mmalloc opcodes rda sim utils Can you please work up a patch for gcc 3.4 to update boehm-gc fastjar gcc libf2c libffi libiberty libjava libobjc libstdc++-v3 zlib And a patch for Insight itcl libgui And one for Dejagnu dejagnu expect And for Newlib & Cygwin libgloss newlib winsup And one for sid and one for intl -- However, I think that it's OK to update one directory at a time, provided we specify clearly what's going on, and get it all done before the next release of anything. Accordingly, I suggest getting clean patches for small sets of directories, making sure they work, getting them reviewed, and then putting them in; and then starting on the next set. Keep sending update notices to the various lists regarding which directories use the 'new' tools and which use the 'old'. If you can make scripts which work correctly under *both* autoconf 2.5x *and* autoconf 2.13, by all means do so *first*, and mark those scripts as "compatibile with both", of course; but I expect that will only happen for the simplest directories. If this is acceptable to other people in the various groups of course. I expect this will generate a certain amount of breakage, but then so did my changes. In both cases, it needs to be done, we just have to make sure all the breakage gets fixed. --Nathanael P.S. It was mentioned that autoconf2.5 scripts will have trouble with building because of the top level passing down --target unconditionally. Unfortunately I think some other aspects of the configure scripts require --target to be passed down unconditionally. :-/ Otherwise I'd just change it.