From: Ian Price <ianprice90@googlemail.com>
To: "" <everfast@126.com>
Cc: bug-guile <bug-guile@gnu.org>, guile-user <guile-user@gnu.org>
Subject: Re: guile 2.0.9 make check error, in bit-operations.test, elisp-compiler.test and eval-string.test
Date: Sun, 20 Oct 2013 22:05:19 +0100 [thread overview]
Message-ID: <87bo2j1wmo.fsf@Kagami.home> (raw)
In-Reply-To: <2013101517050250897627@126.com> (everfast@126.com's message of "Tue, 15 Oct 2013 17:05:05 +0800")
<everfast@126.com> writes:
> The first error emerges at line 1802 in install.output, which reads:
> ERROR: bit-operations.test: bit-extract: documented? - arguments: (
> (keyword-argument-error #<procedure open-input-file
> (file #:key binary encoding guess-encoding)> "Invalid keyword" () #f))
This one is very peculiar, you would have thought that when it threw the
exception it would try to tell you which keywords was invalid.
The documented? test only checks for a result from object-documentation,
so you could you paste the backtrace from
(use-modules (ice-9 documentation))
(object-documentation extract)
You'll need to hit ,bt when you get the prompt. Cheers.
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
next prev parent reply other threads:[~2013-10-20 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 9:05 guile 2.0.9 make check error, in bit-operations.test, elisp-compiler.test and eval-string.test everfast
2013-10-20 21:05 ` Ian Price [this message]
[not found] ` <2013102109434970579116@126.com>
2013-10-24 4:20 ` Ian Price
2016-06-21 11:24 ` bug#15620: " Andy Wingo
2016-06-21 11:51 ` Andy Wingo
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=87bo2j1wmo.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=bug-guile@gnu.org \
--cc=everfast@126.com \
--cc=guile-user@gnu.org \
/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).