all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* bug#15194: hop FTBFS
@ 2013-08-26 21:39 Mark H Weaver
  2013-08-27  8:27 ` Ludovic Courtès
  0 siblings, 1 reply; 6+ messages in thread
From: Mark H Weaver @ 2013-08-26 21:39 UTC (permalink / raw)
  To: 15194

Using guix from git 5d9cd70721aa8256f333f76c76cecc6593b6b293, hop fails
to build from source.  Here's the tail of the make transcript:

--8<---------------cut here---------------start------------->8---
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
--8<---------------cut here---------------end--------------->8---

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#15194: hop FTBFS
  2013-08-26 21:39 bug#15194: hop FTBFS Mark H Weaver
@ 2013-08-27  8:27 ` Ludovic Courtès
  2013-08-27 14:54   ` Mark H Weaver
  0 siblings, 1 reply; 6+ messages in thread
From: Ludovic Courtès @ 2013-08-27  8:27 UTC (permalink / raw)
  To: Mark H Weaver; +Cc: 15194

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’.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#15194: hop FTBFS
  2013-08-27  8:27 ` Ludovic Courtès
@ 2013-08-27 14:54   ` Mark H Weaver
  2013-08-27 15:18     ` Ludovic Courtès
  0 siblings, 1 reply; 6+ messages in thread
From: Mark H Weaver @ 2013-08-27 14:54 UTC (permalink / raw)
  To: Ludovic Courtès; +Cc: 15194

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.

What do you think?

      Mark

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#15194: hop FTBFS
  2013-08-27 14:54   ` Mark H Weaver
@ 2013-08-27 15:18     ` Ludovic Courtès
  2013-08-30  1:35       ` Mark H Weaver
  0 siblings, 1 reply; 6+ messages in thread
From: Ludovic Courtès @ 2013-08-27 15:18 UTC (permalink / raw)
  To: Mark H Weaver; +Cc: 15194

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?

Thanks,
Ludo’.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#15194: hop FTBFS
  2013-08-27 15:18     ` Ludovic Courtès
@ 2013-08-30  1:35       ` Mark H Weaver
  2013-08-30 12:19         ` Ludovic Courtès
  0 siblings, 1 reply; 6+ messages in thread
From: Mark H Weaver @ 2013-08-30  1:35 UTC (permalink / raw)
  To: Ludovic Courtès; +Cc: 15194

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.  I only know about this problem because
I've been building as many Guix packages as possible, for testing
purposes.

     Regards,
       Mark

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#15194: hop FTBFS
  2013-08-30  1:35       ` Mark H Weaver
@ 2013-08-30 12:19         ` Ludovic Courtès
  0 siblings, 0 replies; 6+ messages in thread
From: Ludovic Courtès @ 2013-08-30 12:19 UTC (permalink / raw)
  To: Mark H Weaver; +Cc: 15194-done

Mark H Weaver <mhw@netris.org> skribis:

> 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’.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-08-30 12:20 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-26 21:39 bug#15194: hop FTBFS Mark H Weaver
2013-08-27  8:27 ` Ludovic Courtès
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

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.