hop FTBFS

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Mark H Weaver
Owner
unassigned
Submitted by
Mark H Weaver
Severity
normal
M
M
Mark H Weaver wrote on 26 Aug 2013 23:39
(address . bug-guix@gnu.org)
87sixw5dxx.fsf@tines.lan
Using guix from git 5d9cd70721aa8256f333f76c76cecc6593b6b293, hop fails
to build from source. Here's the tail of the make transcript:

Toggle snippet (24 lines)
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 ...
make[1]: *** [o/xml.o] Error 255
make[1]: Leaving directory `/tmp/nix-build-hop-2.4.0.drv-0/hop-2.4.0/runtime'
make: *** [lib] Error 2
L
L
Ludovic Courtès wrote on 27 Aug 2013 10:27
(name . Mark H Weaver)(address . mhw@netris.org)(address . 15194@debbugs.gnu.org)
87mwo3mtci.fsf@gnu.org
Mark H Weaver <mhw@netris.org> skribis:

Toggle quote (24 lines)
> 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’.
M
M
Mark H Weaver wrote on 27 Aug 2013 16:54
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 15194@debbugs.gnu.org)
87k3j75glw.fsf@tines.lan
ludo@gnu.org (Ludovic Courtès) writes:

Toggle quote (6 lines)
> 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?

I think we should find a solution that doesn't lead to the 'hop' build
being broken every time 'bigloo' is upgraded before 'hop'.

An obvious solution would be to keep two versions of 'bigloo': the
latest release, and the release that corresponds to the latest release
of 'hop'. Hopefully these would be the same most of the time.

What do you think?

Mark
L
L
Ludovic Courtès wrote on 27 Aug 2013 17:18
(name . Mark H Weaver)(address . mhw@netris.org)(address . 15194@debbugs.gnu.org)
87haebgo1v.fsf@gnu.org
Mark H Weaver <mhw@netris.org> skribis:

Toggle quote (15 lines)
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> 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?
>
> I think we should find a solution that doesn't lead to the 'hop' build
> being broken every time 'bigloo' is upgraded before 'hop'.
>
> An obvious solution would be to keep two versions of 'bigloo': the
> latest release, and the release that corresponds to the latest release
> of 'hop'. Hopefully these would be the same most of the time.

Yes, that sounds like a plan. And hopefully the “old” Bigloo would just
differ by its ‘version’ and ‘source’ fields, which is easily handled.

Would you like to propose a patch?

Thanks,
Ludo’.
M
M
Mark H Weaver wrote on 30 Aug 2013 03:35
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 15194@debbugs.gnu.org)
87k3j43qpx.fsf@tines.lan
ludo@gnu.org (Ludovic Courtès) writes:

Toggle quote (22 lines)
> Mark H Weaver <mhw@netris.org> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> 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?
>>
>> I think we should find a solution that doesn't lead to the 'hop' build
>> being broken every time 'bigloo' is upgraded before 'hop'.
>>
>> An obvious solution would be to keep two versions of 'bigloo': the
>> latest release, and the release that corresponds to the latest release
>> of 'hop'. Hopefully these would be the same most of the time.
>
> Yes, that sounds like a plan. And hopefully the “old” Bigloo would just
> differ by its ‘version’ and ‘source’ fields, which is easily handled.
>
> Would you like to propose a patch?

I don't actually use 'bigloo' or 'hop' myself, and right now I have my
hands full with a lot of pending work for Guile, so I'd prefer to let
someone else take care of this. I only know about this problem because
I've been building as many Guix packages as possible, for testing
purposes.

Regards,
Mark
L
L
Ludovic Courtès wrote on 30 Aug 2013 14:19
(name . Mark H Weaver)(address . mhw@netris.org)(address . 15194-done@debbugs.gnu.org)
874na71icd.fsf@gnu.org
Mark H Weaver <mhw@netris.org> skribis:

Toggle quote (28 lines)
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> ludo@gnu.org (Ludovic Courtès) writes:
>>>
>>>> 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?
>>>
>>> I think we should find a solution that doesn't lead to the 'hop' build
>>> being broken every time 'bigloo' is upgraded before 'hop'.
>>>
>>> An obvious solution would be to keep two versions of 'bigloo': the
>>> latest release, and the release that corresponds to the latest release
>>> of 'hop'. Hopefully these would be the same most of the time.
>>
>> Yes, that sounds like a plan. And hopefully the “old” Bigloo would just
>> differ by its ‘version’ and ‘source’ fields, which is easily handled.
>>
>> Would you like to propose a patch?
>
> I don't actually use 'bigloo' or 'hop' myself, and right now I have my
> hands full with a lot of pending work for Guile, so I'd prefer to let
> someone else take care of this.

Message received. ;-)

I used by super powers to fix it in ffc1074.

Thanks!

Ludo’.
Closed
?