From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfc] configury: CC_HAS_UINTPTR_T
Date: Wed, 26 Feb 2003 00:08:00 -0000 [thread overview]
Message-ID: <20030226000809.GA31684@nevyn.them.org> (raw)
In-Reply-To: <200302252321.h1PNLfa13347@duracef.shout.net>
On Tue, Feb 25, 2003 at 05:21:41PM -0600, Michael Elizabeth Chastain wrote:
> This is my first 'configure' patch, so I don't expect it to pass on
> the first draft. If there's anything I need to know about this
> kind of stuff, tell me please.
>
> This patch just adds CC_HAS_UINTPTR_T. After this patch, I'll write
> patches to procfs.c and gdb_thread_db.h to use the new variable, so that
> they can put out a more informative compile error than the dreck that
> they cough up right now. I've seen several reports from the field where
> this actually happens (pr gdb/660 is one case).
Could you call it something different? Autoconfism for this would be
HAVE_UINTPTR_T. You say yourself that it's a property of the C
library, not of the CC.
> +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_c_uintptr_t,
> +[AC_TRY_RUN([
No no. Use AC_TRY_COMPILE; never run a test that you don't actually
need runtime output for.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-26 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 23:21 Michael Elizabeth Chastain
2003-02-26 0:08 ` Daniel Jacobowitz [this message]
2003-02-26 0:17 Michael Elizabeth Chastain
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=20030226000809.GA31684@nevyn.them.org \
--to=drow@mvista.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