From: Kevin Ryde <user42@zip.com.au>
Subject: Re: isinf is a macro on HP-UX
Date: Fri, 28 May 2004 10:48:21 +1000 [thread overview]
Message-ID: <878yfdml62.fsf@zip.com.au> (raw)
In-Reply-To: <B8D7A456-ACCF-11D8-9675-000D93673682@gmx.net> (Andreas Vögele's message of "Sun, 23 May 2004 17:41:56 +0200")
Andreas Vögele <voegelas@gmx.net> writes:
>
> isinf is a macro on HP-UX. Currently, configure.in uses
> AC_CHECK_FUNCS, which checks for functions only, to check for
> isinf.
It's tempting to look only for an isinf macro in the C file. I wonder
if any systems have only a function version.
> I've attached a patch that replaces the current test with a
> test that includes math.h.
I guess the alternative is to leave configure alone and supplement the
result of the test with #ifdef isinf in the C file. Though I suppose
it's a bit disconcerting to see "no" in configure when one's libc docs
say isinf exists.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2004-05-28 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-23 15:41 isinf is a macro on HP-UX Andreas Vögele
2004-05-28 0:48 ` Kevin Ryde [this message]
2004-07-05 0:04 ` Kevin Ryde
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878yfdml62.fsf@zip.com.au \
--to=user42@zip.com.au \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).