[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Guile on Mac OS X

From: Michael Tuexen
Subject: Re: Guile on Mac OS X
Date: Tue, 6 Aug 2002 00:03:02 +0200


oh, I got it. I have to play with configure, not
I will try.

Thank you very much
On Montag, Aug 5, 2002, at 20:23 Europe/Berlin, Rob Browning wrote:

Michael Tuexen <address@hidden> 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

    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,, and
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD


reply via email to

[Prev in Thread] Current Thread [Next in Thread]