Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Manoj Iyer <manjo@austin.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Use HAVE_LONGLONG instead of __GNUC__ to check for long long support.
Date: Tue, 19 Apr 2005 09:54:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0504190525100.10989@lazy> (raw)
In-Reply-To: <7320552869539569@webhare>



> >
> > 2005-04-18  Manoj Iyer  <manjo@austin.ibm.com>
> >         * configure.ac: Added check for long long.
> >         * config.in: Regenerated.
> >         * configure: Regenerated.
> >         * words.h: Modified logic to check for HAVE_LONGLONG instead of
> >         __GNUC__, added config.h header file.
>
> Please use AC_CHECK_TYPES, it should take care of defining
> HAVE_LONG_LONG (note the extra underscore) and the comment all by
> itself.

So I dont need to regenerate config.in if I use AC_CHECK_TYPES? I need to
modify only configure.ac and words.h ? Wondering how HAVE_LONG_LONG will
get added to config.h in this case.

--
Manjo


  reply	other threads:[~2005-04-19  9:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18 22:41 Manoj Iyer
2005-04-18 22:52 ` Daniel Jacobowitz
2005-04-18 23:15   ` Manoj Iyer
2005-04-19  7:58     ` M.M. Kettenis
2005-04-19  9:54       ` Manoj Iyer [this message]
2005-04-19 10:24         ` [RFC] (Resubmit) " Manoj Iyer
2005-04-19 21:33           ` Manoj Iyer
2005-04-19 21:36             ` Daniel Jacobowitz
2005-04-19 21:48               ` Mark Kettenis
2005-04-19 21:50                 ` Daniel Jacobowitz
2005-04-19 21:43             ` Mark Kettenis
2005-04-19 12:33       ` [RFC] " Daniel Jacobowitz
2005-04-19 14:56         ` Manoj Iyer

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=Pine.LNX.4.58.0504190525100.10989@lazy \
    --to=manjo@austin.ibm.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