From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: guile-devel@gnu.org
Subject: Re: Guile on Mac OS X
Date: Mon, 5 Aug 2002 18:37:52 +0200 [thread overview]
Message-ID: <AF96EEFA-A891-11D6-A5EA-0030654C1AB6@lurchi.franken.de> (raw)
In-Reply-To: <874re9xpxk.fsf@raven.i.defaultvalue.org>
Rob,
see my comments below.
Best regards
Michael
On Montag, Aug 5, 2002, at 17:53 Europe/Berlin, Rob Browning wrote:
> Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
>
>>>> 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.
>>>
>> No, see the the following output (from an earlier e-mail):
>
> OK.
>
> What happens if you:
>
> 1) create a tiny C file containing
>
> #include <unistd.h>
> int main(int argc, char *argv[]) { sleep(1); return 0; }
>
> and try to compile it with "gcc -Wall myfile.c"?
No warnings. The program is completely valid:
[Powerbook:~] tuexen% gcc -Wall test.c
[Powerbook:~] tuexen%
>
> 2) Put an AC_EGREP_HEADER([sleep], [unistd.h]) followed by an "exit
> 1" into your configure.in and then re-run autoconf, and then
> re-run configure? After the exit, is there anything useful in
> the log? (may not be).
Well, there is simply no output.
>
> 3) examine the configure script itself -- find the sleep or usleep
> test and see what it's doing. Stick an "exit 1" or some echoes
> in there somewhere useful (if possible) so you can see what's
> going on. I believe if you want to see the output of an echo,
> you will need to redirect it to fd 5 like this:
>
> echo "Howdy!" >&5
>
> This may allow you to see what gcc command it's running, and the
> contents of the relevant source file.
The code which performs the check is:
### 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)
My problem is that it IS working for strptime but NOT for sleep and
usleep and I do not see the difference.
>
> --
> 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
>
>
--
Michael.Tuexen@micmac.franken.de
_______________________________________________
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 16:37 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
2002-08-05 7:44 ` Michael Tuexen
2002-08-05 15:53 ` Rob Browning
2002-08-05 16:37 ` Michael Tuexen [this message]
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=AF96EEFA-A891-11D6-A5EA-0030654C1AB6@lurchi.franken.de \
--to=michael.tuexen@lurchi.franken.de \
--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).