[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [guile-reader-devel] four issues with configure and standard-token-r
From: |
Ludovic Courtès |
Subject: |
Re: [guile-reader-devel] four issues with configure and standard-token-reader |
Date: |
Thu, 19 Mar 2015 21:50:30 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) |
j <address@hidden> skribis:
> 1.
> an error message that appears with configure:
>
> ../pre-inst-guile -l ./extract-doc.scm \
> -c "(apply $main (cdr (command-line)))" ../src/token-readers.h
> Backtrace:
> In ice-9/boot-9.scm:
> 157: 13 [catch #t #<catch-closure 1fad100> ...]
> In unknown file:
> ?: 12 [apply-smob/1 #<catch-closure 1fad100>]
> In ice-9/boot-9.scm:
> 63: 11 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
> 432: 10 [eval # #]
> In unknown file:
> ?: 9 [call-with-input-string "(apply (module-ref (resolve-module
> '(extract-doc)) 'main) (cdr (command-line)))" ...]
> In ice-9/command-line.scm:
> 180: 8 [#<procedure 1fc5a40 at ice-9/command-line.scm:175:6 (port)> #<input:
> string 1d5fa90>]
> In unknown file:
> ?: 7 [eval (apply (module-ref # #) (cdr #)) #<directory (guile-user)
> 1fa3c60>]
> In ice-9/eval.scm:
> 432: 6 [eval # #]
> In ice-9/boot-9.scm:
> 885: 5 [call-with-output-file "token-reader-doc.texi" ...]
> In ice-9/r4rs.scm:
> 176: 4 [with-output-to-port #<variable 20dbc60 value: #<output: file
> /dev/pts/2>> ...]
> In ice-9/eval.scm:
> 432: 3 [eval # #]
> In srfi/srfi-1.scm:
> 619: 2 [for-each #<procedure 1fe6b70 at ice-9/eval.scm:416:20 (a)> #]
> In ice-9/eval.scm:
> 411: 1 [eval # #]
> In unknown file:
> ?: 0 [scm-error misc-error #f ...]
>
> ERROR: In procedure scm-error:
> ERROR: invalid character specification #<unspecified>
I fixed it with
<http://git.savannah.gnu.org/cgit/guile-reader.git/commit/?id=a572bd673026293e9bebb0237e1153d00e345348>
just recently.
Alternately, this can be worked around by running:
LC_ALL=C make
> 2.
> a warning that appears with configure. i am not sure why it should appear
> since i am under the impression to have a standard guile installation (on
> arch linux):
>
> configure: WARNING: `guilemoduledir' (/usr/share/guile/site) is different
> from `GUILE_SITE' (/usr/share/guile/site/2.0).
> configure: WARNING: Make sure to adjust the `GUILE_LOAD_PATH' environment
> variable accordingly,
> configure: WARNING: or re-run `configure' with
> `--with-guilemoduledir=/usr/share/guile/site/2.0'.
If you configure with --with-guilemoduledir=/usr/share/guile/site/2.0 as
it suggests, you’ll be sure that the .scm files from Guile-Reader will
be found automatically; /usr/share/guile/site (the default) actually
works well too but has the disadvantage of being unversioned.
> 3.
> when gnu lightning 2.0.4 or 2.1.0 is installed, configure emits:
> checking for strings.h... (cached) yes
> checking lightning.h usability... yes
> checking lightning.h presence... yes
> checking for lightning.h... yes
> checking whether GNU lightning supports `jit_allocai'... no
> configure: error: Your installation of GNU lightning is too old; install 1.2b
> or later.
Indeed. Fixed in commit 5fa1188.
> 4.
> this code:
> (use-modules (system reader))
> (standard-token-reader (quote boolean))
>
> when evaluated, makes guile display the following. it seems like none of the
> standard token readers works anymore for whatever reason:
> Backtrace:
> In ice-9/boot-9.scm:
> 157: 7 [catch #t #<catch-closure 23e91a0> ...]
> In unknown file:
> ?: 6 [apply-smob/1 #<catch-closure 23e91a0>]
> In ice-9/boot-9.scm:
> 63: 5 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
> 432: 4 [eval # #]
> In ice-9/boot-9.scm:
> 2401: 3 [save-module-excursion #<procedure 2408a00 at ice-9/boot-9.scm:4045:3
> ()>]
> 4052: 2 [#<procedure 2408a00 at ice-9/boot-9.scm:4045:3 ()>]
> In unknown file:
> ?: 1 [load-compiled/vm
> "/home/nonroot/.cache/guile/ccache/2.0-LE-8-2.0/mnt/sdb1/stor/temp/guile.scm.go"]
> ?: 0 [standard-token-reader boolean]
>
> ERROR: In procedure standard-token-reader:
> ERROR: In procedure standard-token-reader: not a standard token reader:
> boolean
This stems from the same problem as #1.
Thanks for the report!
Ludo’.