From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8598 invoked by alias); 13 Jan 2003 07:31:05 -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 8573 invoked from network); 13 Jan 2003 07:31:02 -0000 Received: from unknown (HELO egil.codesourcery.com) (66.92.14.122) by 209.249.29.67 with SMTP; 13 Jan 2003 07:31:02 -0000 Received: from zack by egil.codesourcery.com with local (Exim 3.36 #1 (Debian)) id 18Xz3X-00031U-00; Sun, 12 Jan 2003 23:30:47 -0800 To: Klee Dienes Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com, newlib@sources.redhat.com, gcc@gcc.gnu.org, sid@sources.redhat.com Subject: Re: [RFC] Update to current automake/autoconf/libtool versions (take 2) From: Zack Weinberg Date: Mon, 13 Jan 2003 07:31:00 -0000 In-Reply-To: <95057BBA-26A7-11D7-B338-00039396EEB8@apple.com> (Klee Dienes's message of "Sun, 12 Jan 2003 22:32:03 -0500") Message-ID: <87smvxo6ag.fsf@egil.codesourcery.com> User-Agent: Gnus/5.090011 (Oort Gnus v0.11) Emacs/21.2 (i386-pc-linux-gnu) References: <95057BBA-26A7-11D7-B338-00039396EEB8@apple.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-01/txt/msg00483.txt.bz2 Klee Dienes writes: > The original theory was that I was trying to keep the diffs to a > minimum, and that once the switch was flipped on 2.x, we could go back > and make a lot of more interesting cleanups to the configure scripts. That's fair... > But I think you're right that my changes ended up complicated enough > that I should just replace them with the modern versions; I'll do > that. It may actually make sense to do the replacement as a separate patch, introducing a shared aclocal.m4 fragment that backports AC_NO_EXECUTABLES or similar to 2.13. Put that in first, and your diffs for the 2.5x conversion get quite a bit simpler. > I didn't disable the config.cache in the top-level scripts; it's > just that the new default is for autoconf to use a null cache file > unless configured with '-C'. I may have misunderstood your patch but I got the definite impression that you dropped out the only bit that passes down the top-level --cache-file setting to the sub-configures. Which would mean, even if the top level was run with -C, the sub-configures would use no cache file, and wouldn't share caches if they did. The change of default is wrong, but that's not your fault. > I did disable the target config.cache, because there were places > where things really were being run with different flags between runs > (for example, the value of libstdcxx_flags varies by directory), and > fixing that seemed beyond the scope of the initial conversion to 2.5x. Yeah, that's reasonable. We'll want it back eventually though. zw