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

>  > > * acinclude.m4 (AM_PROG_CC_STDC): New macro to override the broken
>   > > one in automake.  Uses -Ae, not -Aa to put HP compiler into ANSI
>   > > with extensions mode.
>   > > * aclocal.m4: Rebuilt.
>   > > > > > Mostly ok.  Before checking it in can you please tweek the name to be 
>   > something else (GDB_PROG_CC_STDC?) and modify the description to mention 
>   > how it is different to AM_PROG_CC_STDC.
> 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.


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.


> I haven't followed things closely enough to know if that's viable or not
> (not to mention my lack of knowledge regarding autoconf/automake).


Ditto.  Tom?


>   > Are you able to pull this into the 5.1 branch or do you want me to?
> I can if we in fact do need a CC_STDC definition for gdb.



Andrew




  reply	other threads:[~2001-12-19 10:06 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 [this message]
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

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=3C206691.2010005@cygnus.com \
    --to=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