From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Guile on Mac OS X
Date: Mon, 05 Aug 2002 00:24:16 -0500 [thread overview]
Message-ID: <87n0s1yj27.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <5C6B8E44-A7DC-11D6-900A-0030654C1AB6@lurchi.franken.de> (Michael Tuexen's message of "Sun, 4 Aug 2002 20:59:53 +0200")
Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
> ### GUILE_FUNC_DECLARED(function, headerfile)
> ### Check for a declaration of FUNCTION in HEADERFILE; if it is
> ### not there, #define MISSING_FUNCTION_DECL.
> AC_DEFUN(GUILE_FUNC_DECLARED, [
> AC_CACHE_CHECK(for $1 declaration, guile_cv_func_$1_declared,
> AC_EGREP_HEADER($1, $2,
> guile_cv_func_$1_declared=yes,
> guile_cv_func_$1_declared=no))
> if test [x$guile_cv_func_]$1[_declared] = xno; then
> AC_DEFINE([MISSING_]translit($1, [a-z], [A-Z])[_DECL])
> fi
> ])
>
> GUILE_FUNC_DECLARED(strptime, time.h)
> GUILE_FUNC_DECLARED(sleep, unistd.h)
> GUILE_FUNC_DECLARED(usleep, unistd.h)
Looks like usleep and sleep are in unistd.h on (most?) platforms, but
on yours they're in time.h.
Unfortunately GUILE_FUNC_DECLARED may not make it easy to test a
second location since it looks like if the function isn't found the
first time, it takes actions that wouldn't be undone by a later
successful test.
One option would be to change GUILE_FUNC_DECLARED to allow multiple
headers like this:
GUILE_FUNC_DECLARED([sleep], [unistd.h time.h])
or can m4, etc. handle ... args?
GUILE_FUNC_DECLARED([sleep], [unistd.h], [time.h])
I'll look in to a solution of some kind unless someone else knows how
to write this up off the top of their head.
Alternately I suppose we could use two functions, one to check a
header and one to call later to take action if none of the checks
succeeded:
GUILE_CHECK_HEADER_FOR_FUNC([sleep], [unistd.h])
GUILE_CHECK_HEADER_FOR_FUNC([sleep], [time.h])
GUILE_CHECK_FOR_MISSING_FUNC_DECLARATION([sleep])
not a big deal to me either way.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-05 5:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87znw2xy71.fsf@raven.i.defaultvalue.org>
2002-08-04 18:59 ` Guile on Mac OS X Michael Tuexen
2002-08-05 5:24 ` Rob Browning [this message]
2002-08-05 7:44 ` Michael Tuexen
2002-08-05 15:53 ` Rob Browning
2002-08-05 16:37 ` Michael Tuexen
2002-08-05 18:23 ` Rob Browning
2002-08-05 22:03 ` Michael Tuexen
2002-08-04 12:34 Michael Tuexen
2002-08-04 18:21 ` Rob Browning
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=87n0s1yj27.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
/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).