Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: law@redhat.com
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Update for AC_PROG_STDC_CC fix
Date: Wed, 19 Dec 2001 08:30:00 -0000	[thread overview]
Message-ID: <21214.1008779331@porcupine.cygnus.com> (raw)
In-Reply-To: Your message of Wed, 19 Dec 2001 10:06:09 GMT. <3C206691.2010005@cygnus.com>

  > Isn't something needed for HP/UX to get the compiler into the right 
  > mode?  But yes I agree, even after renaming the macro, there is a 
  > problem with prog_cc_stdc clashes.
True, that would be a problem.  I wouldn't have mentioned the idea of
zapping AM_PROG_CC_STDC except for the fact that I couldn't figure out
if/how it would ever be used.

It seems to me like the various Makefiles associated with gdb use CC,
but I couldn't find the mechanism by which CC was assigned the result
of AM_PROG_CC_STDC.  But apparently by some magic it does happen.

This in turn begs the question -- if we rename AM_PROG_CC_STDC to
GDB_PROG_CC_STDC will the value computed by GDB_PROG_CC_STDC still
be used to initialize CC in the generated Makefile?

I can try some experiments, but it would really be better if someone
who understands autoconf/automake better could give me some insight
into what unintended consequences we might have due to the name change.

jeff


  reply	other threads:[~2001-12-19 16:30 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 [this message]
2001-12-19  9:59         ` Tom Tromey
2001-12-19  9:29       ` Tom Tromey
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=21214.1008779331@porcupine.cygnus.com \
    --to=law@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@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