Re: FAIL: test-use-srfi (Leopard)

[Ludovic Courtès]

Hi,

Alexander Asteroth <address@hidden> writes:

> OK, I managed getting guile-1.8.5 compiled on Mac OS X Leopard.
>
> Since gmp-4.2.2 detected 64 bit (and compilation failed with ABI=32) I
> configured guile with CLFLAGS=-m64. After using make LIBTOOL=/usr/
> local/bin/libool (to get libtool-2.2.2) compilation succeeded
> successfully.

So you didn't have to modify the source at all, right?

> Backtrace:
> In unknown file:
>    ?: 133* [#<procedure #f ()>]
>    ?: 134* [load-file #<primitive-procedure primitive-load> ...]
>    ?: 135* [save-module-excursion #<procedure #f ()>]
>    ?: 136  (let (# #) (dynamic-wind # thunk #))
>    ?: 137  [dynamic-wind #<procedure #f ()> #<procedure #f ()>
> #<procedure #f ()>]
>    ?: 138* [#<procedure #f ()>]
>    ?: 139* [primitive-load "/Users/aster/src/guile-1.8.5/ice-9/
> debug.scm"]
> In /Users/aster/src/guile-1.8.5/ice-9/debug.scm:
>   22: 140* (define-module (ice-9 debug) :export ...)
> In unknown file:
>    ?: 141* [copy-tree ...
>    ?: 142* [apply #<procedure #f args> (# :export #)]
>    ?: 143  [#<procedure #f args> (ice-9 debug) :export ...]
>    ?: 144  (quasiquote (eval-case (# #) (else #)))
>    ?: 145* [compile-define-module-args (# :export #)]
>    ?: 146  [loop ((quote #)) (:export (frame-number->index trace
> untrace ...))]
>      ...
>    ?: 147  [loop ((quote (ice-9 debug))) ...
>    ?: 148* [cons ...
>    ?: 149* [keyword-like-symbol->keyword :export]
>    ?: 150  [symbol->keyword ...
>    ?: 151* [string->symbol ...
>    ?: 152* (substring (symbol->string sym) 1)
>
> <unnamed port>: In expression (substring (symbol->string sym) 1):
> <unnamed port>: Stack overflow

This indicates that the default Scheme stack depth limit is too low for
your platform.  Can you try the patch provided in the following message:

  http://permalink.gmane.org/gmane.lisp.guile.devel/7221

It implements automatic calibration of the stack depth limit.  You can
apply it by typing:

  cd guile-1.8.5
  patch -p0 < /path/to/the-patch.diff

As a side effect it will produce debugging output about the stack
calibration process; can you also report that output?

Thanks in advance,
Ludovic.