From: Mark H Weaver <mhw@netris.org>
To: tantalum <sph@posteo.eu>
Cc: 21614-done@debbugs.gnu.org
Subject: bug#21614: add-to-load-path compilation fails with compile-cps error
Date: Tue, 06 Oct 2015 10:14:15 -0400 [thread overview]
Message-ID: <877fn0t77s.fsf@netris.org> (raw)
In-Reply-To: <56115721.1020704@posteo.eu> (tantalum's message of "Sun, 4 Oct 2015 16:43:13 +0000")
tantalum <sph@posteo.eu> writes:
> i am getting a compilation error which seems odd to me, with guile
> version 2.1.0.455-73f61, compiled from the commit from 2015-09-18.
[...]
> # from the repl
>
> scheme@(guile-user)> (add-to-load-path "test")
> While compiling expression:
> ERROR: Wrong number of arguments to #<procedure 1877c00 at language/tree-il/compile-cps.scm:463:7 (val)>
> scheme@(guile-user)>
I believe this is fixed in commit 315adb6347. I'm closing this bug, but
please let me know if you continue to have problems.
Thanks!
Mark
prev parent reply other threads:[~2015-10-06 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 16:43 bug#21614: add-to-load-path compilation fails with compile-cps error tantalum
2015-10-06 14:14 ` Mark H Weaver [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=877fn0t77s.fsf@netris.org \
--to=mhw@netris.org \
--cc=21614-done@debbugs.gnu.org \
--cc=sph@posteo.eu \
/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).