Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: law@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: Update for AC_PROG_STDC_CC fix
Date: Wed, 19 Dec 2001 09:29:00 -0000	[thread overview]
Message-ID: <87pu5b6rjv.fsf@creche.redhat.com> (raw)
In-Reply-To: Andrew Cagney's message of "Wed, 19 Dec 2001 10:06:09 +0000"

>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:

>> Or better yet, can we get rid of it completely from GDB?   The only reason
>> this causes problems is the bogus definition of prog_cc_stdc found when
>> configuring gdb bleeds into other directories which use prog_cc_stdc
>> via a shared config.cache.

Andrew> Isn't something needed for HP/UX to get the compiler into the right 
Andrew> mode?  But yes I agree, even after renaming the macro, there is a 
Andrew> problem with prog_cc_stdc clashes.

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.

HTH,
Tom


  parent reply	other threads:[~2001-12-19 17:29 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 [this message]
2001-12-19  9:55         ` law

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=87pu5b6rjv.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=law@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