From: Andy Wingo <wingo@pobox.com>
To: 15620-done@debbugs.gnu.org
Subject: bug#15620: guile 2.0.9 make check error, in bit-operations.test, elisp-compiler.test and eval-string.test
Date: Tue, 21 Jun 2016 13:51:00 +0200 [thread overview]
Message-ID: <87a8ie221n.fsf@pobox.com> (raw)
In-Reply-To: <87pora2391.fsf@pobox.com> (Andy Wingo's message of "Tue, 21 Jun 2016 13:24:58 +0200")
close
thanks
On Tue 21 Jun 2016 13:24, Andy Wingo <wingo@pobox.com> writes:
> Hi Frank,
>
> Closing this one due to lack of information. If you find a compile
> failure with icc on Guile 2.0.11 or 2.1.3, please open a new report.
> Thanks :)
>
> Andy
>
> On Thu 24 Oct 2013 06:20, Ian Price <ianprice90@googlemail.com> writes:
>
>> "" <everfast@126.com> writes:
>>
>>> Thanks, Ian.
>>>
>>> For me compiling guile is just to satisfy a dependency of another
>>> software. I am really not
>>> familiar with guile.
>>>
>>>>(use-modules (ice-9 documentation))
>>>>(object-documentation extract)
>>> Do you mean a file in the compiling-folder/module/ice-9? I have no
>>> idea which one will be.
>>> All files in such folder are compressed and attached. Also attached is
>>> install script and logs.
>>
>> I mean, run guile, and enter those two forms at the prompt, followed by
>> return. Since this is the code in the test that gives an error, you
>> should hopefully get an error here too. Then you can use the command ,bt
>> to get a backtrace.
prev parent reply other threads:[~2016-06-21 11:51 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
[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 [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=87a8ie221n.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=15620-done@debbugs.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).