From: law@redhat.com
To: tromey@redhat.com
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: Update for AC_PROG_STDC_CC fix
Date: Wed, 19 Dec 2001 09:55:00 -0000 [thread overview]
Message-ID: <21676.1008784410@porcupine.cygnus.com> (raw)
In-Reply-To: Your message of 19 Dec 2001 10:36:04 MST. <87pu5b6rjv.fsf@creche.redhat.com>
> I think clashes should only be a problem if you are using different
> versions of this macro in different directories. If so, that's a
> no-no. It has always been the case that all configure scripts in a
> given project must agree about how to compute cache values. I think
> this is an undocumented requirement :-(, but careful examination of
> the ChangeLogs will show bug fixes for problems like this dating back
> at least to 1996.
Right. Which is precisely why I'm in this situation to begin with --
"make" has its own version, which was wrong, but at least was closer
to being correct.
After fixing the version in the "make" subdir I was surprised to find
that my fix didn't work. Which led me to gdb and the shared cache problems...
And through the discussion we find out that anyone using the one directly
from autoconf-1.4 is getting a broken version.
Until autoconf-1.5 is released we probably should be overriding the default
version. The only question in my mind is how best to do that. Do we
keep the original name, or do we use a new one? What affect (if any) does
changing the name have on the magic which uses the result of PROG_CC_STDC
to initialize CC in the generated Makefile?
jeff
prev parent reply other threads:[~2001-12-19 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 9:48 law
2001-12-18 12:35 ` Andrew Cagney
2001-12-18 12:51 ` law
2001-12-19 2:06 ` Andrew Cagney
2001-12-19 8:30 ` law
2001-12-19 9:59 ` Tom Tromey
2001-12-19 9:29 ` Tom Tromey
2001-12-19 9:55 ` law [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=21676.1008784410@porcupine.cygnus.com \
--to=law@redhat.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@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