From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [rfc] configury: CC_HAS_UINTPTR_T
Date: Wed, 26 Feb 2003 00:17:00 -0000 [thread overview]
Message-ID: <200302260017.h1Q0H4v14234@duracef.shout.net> (raw)
Hi Daniel,
mec> Could you call it something different? Autoconfism for this would be
mec> HAVE_UINTPTR_T. You say yourself that it's a property of the C
mec> library, not of the CC.
No problem.
mec> +[AC_TRY_RUN([
drow> No no. Use AC_TRY_COMPILE; never run a test that you don't actually
drow> need runtime output for.
I suppose that's a cross issue (because we can cross-compile but not
cross-run).
I originally wrote this with AC_TRY_COMPILE but it failed, because
AC_TRY_COMPILE wraps an "int main () { ... }" around its argument.
Err wait, two minutes with 'info automake' and I am enlightened.
Doh!
Thanks,
Michael C
next reply other threads:[~2003-02-26 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 0:17 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-25 23:21 Michael Elizabeth Chastain
2003-02-26 0:08 ` Daniel Jacobowitz
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=200302260017.h1Q0H4v14234@duracef.shout.net \
--to=mec@shout.net \
--cc=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