From: Klee Dienes <klee@apple.com>
To: Zack Weinberg <zack@codesourcery.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 03:32:00 -0000 [thread overview]
Message-ID: <95057BBA-26A7-11D7-B338-00039396EEB8@apple.com> (raw)
In-Reply-To: <87of6mp9yi.fsf@egil.codesourcery.com>
On Sunday, January 12, 2003, at 12:13 PM, Zack Weinberg wrote:
> 1) I notice that you made the existing pseudo-AC_PROG_CC/CXX macros
> work again with 2.5x; this is wrong. Get rid of them entirely,
> use the canonical AC_PROG_CC/CXX, and if they don't work right,
> patch autoconf until they do.
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.
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.
> 2) Why did you disable the shared config.cache? It speeds up 'make
> configure' by an order of magnitude, especially on slow machines.
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'. A good portion of my patch is actually present
solely to fix the use of a top-level cache file --- there were a number
of places where whitespace triggered the "value changed between runs"
checks in 2.5x. 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.
next prev parent reply other threads:[~2003-01-13 3:32 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 [this message]
2003-01-13 7:31 ` Zack Weinberg
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=95057BBA-26A7-11D7-B338-00039396EEB8@apple.com \
--to=klee@apple.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=newlib@sources.redhat.com \
--cc=sid@sources.redhat.com \
--cc=zack@codesourcery.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).