From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: guile-devel@gnu.org
Subject: Re: Guile on Mac OS X
Date: Tue, 6 Aug 2002 00:03:02 +0200 [thread overview]
Message-ID: <1CAE489A-A8BF-11D6-A5EA-0030654C1AB6@lurchi.franken.de> (raw)
In-Reply-To: <87ofchw4fe.fsf@raven.i.defaultvalue.org>
Rob,
oh, I got it. I have to play with configure, not configure.in.
I will try.
Thank you very much
Michael
On Montag, Aug 5, 2002, at 20:23 Europe/Berlin, Rob Browning wrote:
> Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
>
>> The code which performs the check is:
>
> This is not the code in the resulting configure file. That code will
> be expanded, and I believe if you search for usleep, you'll find it in
> a for loop like this:
>
> for ac_func in ctermid ftime fchown getcwd geteuid gettimeofday
> lstat mkdir mknod nice readlink rename rmdir select setegid seteuid
> setlocale setpgid setsid sigaction siginterrupt strftime strptime
> symlink sync tcgetpgrp tcsetpgrp times uname waitpid strdup system
> usleep atexit on_exit chown link fcntl ttyname getpwent getgrent kill
> getppid getpgrp fork setitimer getitimer
>
> do
> as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh`
> echo "$as_me:$LINENO: checking for $ac_func" >&5
> echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6
> ...
>
> That's where I'm talking about adding the echo/exit/whatever debugging
> statements and then re-running configure. If you try this, make sure
> you rm config.cache between runs.
>
>> My problem is that it IS working for strptime but NOT for sleep and
>> usleep and I do not see the difference.
>
> Right. My guess is that there may be some preprocessor #ifdefery or
> something causing the trouble. If you can use the above tricks to
> actually see the code it's running to test you should be able to run
> that code directly from a prompt and see what the actual gcc/cpp error
> msgs are, if any.
>
> --
> 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 22:03 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
2002-08-05 18:23 ` Rob Browning
2002-08-05 22:03 ` Michael Tuexen [this message]
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=1CAE489A-A8BF-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).