From: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
To: Manoj Iyer <manjo@austin.ibm.com>, 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 07:58:00 -0000 [thread overview]
Message-ID: <7320552869539569@webhare> (raw)
In-Reply-To: <Pine.LNX.4.58.0504181843310.29047@lazy>
Manoj Iyer <manjo@austin.ibm.com> wrote:
>
> Daniel,
>
> Used autoheader to generate the config.in file, but it does not look
> pretty, also, removed the comments that you did not like.
>
> 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.
> --- src/sim/ppc/configure.ac 2005-01-12 10:23:21.000000000 -0600
> +++ new/src/sim/ppc/configure.ac 2005-04-18 18:34:10.000000000 -0500
> @@ -681,6 +681,9 @@ if test $ac_cv_struct_statfs = yes; then
> [Define if struct statfs is defined in <sys/mount.h>])
> fi
>
> +AC_CHECK_TYPE(long long,
> + AC_DEFINE(HAVE_LONGLONG, 1, [Define if compiler supports long long.]),)
> +
> dnl Figure out if /dev/zero exists or not
> sim_devzero=""
> AC_MSG_CHECKING(for /dev/zero)
next prev parent reply other threads:[~2005-04-19 7:58 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 [this message]
2005-04-19 9:54 ` Manoj Iyer
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=7320552869539569@webhare \
--to=m.m.kettenis@alumnus.utwente.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=manjo@austin.ibm.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