From: Zack Weinberg <zack@codesourcery.com>
To: Klee Dienes <klee@apple.com>
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)
Date: Mon, 13 Jan 2003 07:31:00 -0000 [thread overview]
Message-ID: <87smvxo6ag.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <95057BBA-26A7-11D7-B338-00039396EEB8@apple.com> (Klee Dienes's message of "Sun, 12 Jan 2003 22:32:03 -0500")
Klee Dienes <klee@apple.com> 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
prev parent reply other threads:[~2003-01-13 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021205190728.GA11507@doctormoo>
2003-01-12 10:32 ` Klee Dienes
2003-01-12 16:14 ` Nathanael Nerode
2003-01-12 17:14 ` Zack Weinberg
2003-01-13 3:32 ` Klee Dienes
2003-01-13 7:31 ` Zack Weinberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87smvxo6ag.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=klee@apple.com \
--cc=newlib@sources.redhat.com \
--cc=sid@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).