Re: Guile on Mac OS X

[Michael Tuexen]

Rob,

thank you for your response. I looked a bit into this. Maybe some
can give me a hint...

The output of the configure script is

checking for crypt in -lcrypt... no
checking for strptime declaration... yes
checking for sleep declaration... no
checking for usleep declaration... no

But the declarations are there. See

[Powerbook:~/guile-1.5.6] tuexen% grep strptime /usr/include/time.h
char *strptime __P((const char *, const char *, struct tm *));
[Powerbook:~/guile-1.5.6] tuexen% grep sleep /usr/include/unistd.h
unsigned int     sleep __P((unsigned int));
int      usleep __P((unsigned int));
[Powerbook:~/guile-1.5.6] tuexen% grep usleep /usr/include/unistd.h
int      usleep __P((unsigned int));
[Powerbook:~/guile-1.5.6] tuexen%

The config.log gives no read help:

configure:10836: result: no
configure:10855: checking for strptime declaration
configure:10875: result: yes
configure:10884: checking for sleep declaration
configure:10904: result: no
configure:10913: checking for usleep declaration
configure:10933: result: no

The code in the configure.in is the following

### Some systems don't declare some functions.  On such systems, we
### need to at least provide our own K&R-style declarations.

### 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)

Any help is welcome.

Best regards
Michael

On Sonntag, Aug 4, 2002, at 20:42 Europe/Berlin, Rob Browning wrote:

> Michael Tuexen <address@hidden> writes:
>
> > see my comments below.
>
> Thanks.  I'll look at this in a bit.  BTW, in general, if you don't
> mind, it might be better to send info like this to the list -- that
> way if I drop the ball (get too busy or whatever), someone else will
> be able to fix the problem.
>
> No big deal 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
--
address@hidden