Alan Grover <[EMAIL PROTECTED]> writes:
>
> The ice-9/slib.scm module should be removed. It appears to be broken.
Bit rot :(.
> The Guile documentation should refer to the SLIB README file (sections
> on loading the initialization file, and implementation specific
> instructions).
Yep.
> These
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> BTW, this script sets `GUILE_LOAD_PATH' to `${top_srcdir}/test-suite'
> only. Consequently, the `ice-9' modules (and in particular
> `boot-9.scm') are loaded from `${datadir}/guile/1.7', /not/ from the
> source tree, which is wrong.
Did you try it (
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> When running `elisp.test' untouched. Here's what I get:
>
> $ guile -L .. -l tests/elisp.test
> [...]
> PASS: scheme: value preservation: cdr
> PASS: scheme: value preservation: vector-ref
> ERROR: Stack overflow
I can't reproduce this, but
Kevin Ryde wrote:
> Alan Grover <[EMAIL PROTECTED]> writes:
>
>>Summary: The documentation on SLIB use is inadequate and/or out-of-date
>>Guile version 1.6.4, "edition 1.0 of the reference manual, corresponding
>>to Guile version 1.6.4"
>
>
> That stuff hasn't been kept up to date, and the slib
Hi,
Neil Jerram <[EMAIL PROTECTED]> writes:
> Actually I'm not sure I understand. Do you see the stack overflow
> only after applying your patch, or did it occur before the patch also
> on your system? I don't see a problem on Intel using current CVS.
When running `elisp.test' untouched. Here
Hi,
Kevin Ryde <[EMAIL PROTECTED]> writes:
> It is, but from the top-level ./check-guile.
Ah, I see.
BTW, this script sets `GUILE_LOAD_PATH' to `${top_srcdir}/test-suite'
only. Consequently, the `ice-9' modules (and in particular
`boot-9.scm') are loaded from `${datadir}/guile/1.7', /not/ from
