From: Andy Wingo <wingo@pobox.com>
To: David Pirotte <david@altosw.be>
Cc: 10567-done@debbugs.gnu.org
Subject: bug#10567: Fw: guile-library - make bug report
Date: Sat, 02 Mar 2013 23:16:05 +0100 [thread overview]
Message-ID: <874ngt8n2y.fsf@pobox.com> (raw)
In-Reply-To: <87sjirj554.fsf@pobox.com> (Andy Wingo's message of "Fri, 03 Feb 2012 16:41:43 +0100")
On Fri 03 Feb 2012 16:41, Andy Wingo <wingo@pobox.com> writes:
> On Fri 20 Jan 2012 19:25, David Pirotte <david@altosw.be> writes:
>
>> guile 2.0.3.150-88c0
>> guile-lib release-0.2.1-2-ge9fe22b
>>
>> ...
>> make[1]: Entering directory `/usr/local/src/guile-lib/git-clone/src'
>> ../dev-environ /usr/local/bin/guile-tools compile -o "text/parse-lalr.go"
>> "text/parse-lalr.scm" ice-9/boot-9.scm:106:20: In procedure #<procedure 9a66680 at
>> ice-9/boot-9.scm:97:6 (thrown-k . args)>: ice-9/boot-9.scm:106:20: In procedure
>> scm_read_expression: text/parse-lalr.scm:1418:45: unexpected ")" make[1]: ***
>> [text/parse-lalr.go] Error 1 make[1]: Leaving directory
>> `/usr/local/src/guile-lib/git-clone/src' make: *** [all-recursive] Error 1
>
> The line in question:
>
> (eq? (car rest) ':)
>
> It seems you have (read-set! keywords 'prefix) in your init.scm, which
> affects the compile-time environment.
>
> I wonder what is the right thing to do here.
In this case, probably just to change it to (string->symbol ":"). I
have done that. We don't need to change the copy in Guile because its
compilation environment is more controlled.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2013-03-02 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 18:25 bug#10567: Fw: guile-library - make bug report David Pirotte
2012-02-03 15:41 ` Andy Wingo
2012-02-04 16:29 ` David Pirotte
2013-03-02 22:16 ` Andy Wingo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874ngt8n2y.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=10567-done@debbugs.gnu.org \
--cc=david@altosw.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).