From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 15194@debbugs.gnu.org
Subject: bug#15194: hop FTBFS
Date: Tue, 27 Aug 2013 10:27:25 +0200 [thread overview]
Message-ID: <87mwo3mtci.fsf@gnu.org> (raw)
In-Reply-To: <87sixw5dxx.fsf@tines.lan> (Mark H. Weaver's message of "Mon, 26 Aug 2013 17:39:54 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> Using guix from git 5d9cd70721aa8256f333f76c76cecc6593b6b293, hop fails
> to build from source. Here's the tail of the make transcript:
>
> bigloo -O2 -fsharing -Wall -wslots -L /tmp/nix-build-hop-2.4.0.drv-0/hop-2.4.0/lib -srfi enable-threads -srfi enable-avahi -cc gcc -copt "-O3 -I/nix/store/l4389c6kqs5x339ai7rah7ywaxm97hcs-bigloo-4.0b/lib/bigloo/4.0b" -srfi hop-dynamic -copt -fPIC -L /tmp/nix-build-hop-2.4.0.drv-0/hop-2.4.0/lib -unsafe -safee -c xml.scm -o o/xml.o
>
> File "xml.scm", line 859, character 33481:
> # (let ((js-attr (xml-attribute-encode (xml-tilde->statement obj))))
> # ^
> *** ERROR:xml-tilde->attribute
> Unbound variable -- xml-attribute-encode
>
> File "xml.scm", line 646, character 24544:
> # (let ((a (xml-attribute-encode attr)))
> # ^
> *** ERROR:xml-write-attribute1293
> Unbound variable -- xml-attribute-encode
>
> File "xml.scm", line 650, character 24709:
> # (display (xml-attribute-encode attr) p)))
> # ^
> *** ERROR:xml-write-attribute1293
> Unbound variable -- xml-attribute-encode
> 3 errors occured, ending ...
Yes, that’s a consequence of the Bigloo upgrade
(e858326a0f8574e98336046752a4bf786a2c1d0a). It turns out Hop & Bigloo
have to be upgraded in lockstep. I believe a new Hop version is around
the corner, so I’m tempted to just wait for that.
WDYT?
Ludo’.
next prev parent reply other threads:[~2013-08-27 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 21:39 bug#15194: hop FTBFS Mark H Weaver
2013-08-27 8:27 ` Ludovic Courtès [this message]
2013-08-27 14:54 ` Mark H Weaver
2013-08-27 15:18 ` Ludovic Courtès
2013-08-30 1:35 ` Mark H Weaver
2013-08-30 12:19 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mwo3mtci.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=15194@debbugs.gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.