From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com
Subject: [rfa] HAVE_UINTPTR_T
Date: Wed, 26 Feb 2003 01:26:00 -0000 [thread overview]
Message-ID: <200302260126.h1Q1Qd715234@duracef.shout.net> (raw)
Draft #2. I changed the variable to HAVE_UINTPTR_T, and I changed
AC_TRY_RUN to AC_TRY_COMPILE. I re-tested with and without
uintptr_t in /usr/include/stdint.h to hit both paths.
I don't show diffs for regenerated 'configure'. I regenerated
'configure' with stock autoconf 2.13 from ftp.gnu.org.
Again, this is so that the gdb build can do something better when
it needs uintptr_t and doesn't have it (pr gdb/660). My notion of
'something better' is going to be to spit out a better error message,
not to actually work. Somebody has to have a really old libc
(more than 3 years old) to get this message, but with millions of
users, some people do.
OK to commit?
Michael C
2003-02-25 Michael Chastain <mec@shout.net>
* configure.in: New variable HAVE_UINTPTR_T.
* config.in: Likewise.
* configure: Regenerated.
Index: config.in
===================================================================
RCS file: /cvs/src/src/gdb/config.in,v
retrieving revision 1.53
diff -u -r1.53 config.in
--- config.in 14 Feb 2003 20:07:00 -0000 1.53
+++ config.in 26 Feb 2003 01:20:51 -0000
@@ -111,6 +111,9 @@
/* Define if ioctl argument PIOCSET is available. */
#undef HAVE_PROCFS_PIOCSET
+/* Define if the C library supports "uintptr_t" type. */
+#undef HAVE_UINTPTR_T
+
/* Define if the `long long' type works. */
#undef CC_HAS_LONG_LONG
Index: configure.in
===================================================================
RCS file: /cvs/src/src/gdb/configure.in,v
retrieving revision 1.125
diff -u -r1.125 configure.in
--- configure.in 20 Feb 2003 23:38:58 -0000 1.125
+++ configure.in 26 Feb 2003 01:20:52 -0000
@@ -689,6 +689,21 @@
fi
fi
+dnl See if C library supports "uintptr_t" type.
+dnl AC_CHECK_TYPE is not enough because this type lives in a header file.
+
+AC_MSG_CHECKING(for uintptr_t in C library)
+AC_CACHE_VAL(gdb_cv_have_uintptr_t,
+[AC_TRY_COMPILE([#include <stdint.h>],
+ [uintptr_t foo = 0;
+ return foo;],
+ gdb_cv_have_uintptr_t=yes,
+ gdb_cv_have_uintptr_t=no)])
+AC_MSG_RESULT($gdb_cv_have_uintptr_t)
+if test $gdb_cv_have_uintptr_t = yes; then
+ AC_DEFINE(HAVE_UINTPTR_T)
+fi
+
dnl See if compiler supports "long long" type.
AC_MSG_CHECKING(for long long support in compiler)
next reply other threads:[~2003-02-26 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 1:26 Michael Elizabeth Chastain [this message]
2003-02-26 3:08 ` Daniel Jacobowitz
2003-02-26 13:07 ` Andreas Schwab
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=200302260126.h1Q1Qd715234@duracef.shout.net \
--to=mec@shout.net \
--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