This is the mail archive of the
guile-gtk@sources.redhat.com
mailing list for the Guile project.
Re: Taming the beast [was: Re: guile-gobject 0.3.0 Released]
>>>>> "rm" == rm <rm@fabula.de> writes:
rm> | make[2]: Entering directory `/home/ralf/projects/guile-gobject-0.3.0/gobject'
rm> | FLAVOR=gnome guile -c \
rm> | "(set! %load-path (cons \"..\" %load-path)) \
rm> | (primitive-load \"./gnome-gobject.gwp\")"
rm> | ERROR: Unbound variable: nil
rm> | make[2]: *** [gnomegobject.h] Error 2
rm> | make[2]: Leaving directory `/home/ralf/projects/guile-gobject-0.3.0/gobject'
rm> | make[1]: *** [all-recursive] Error 1
rm> | make[1]: Leaving directory `/home/ralf/projects/guile-gobject-0.3.0'
rm> | make: *** [all-recursive-am] Error 2
rm> |
rm> Hmm, no idea where 'nil' is supposed to come from.
rm> A quick grep didn't reveal anything. Ariel, any hints?
Aha, fame at last! I removed `nil' from libguile, because its only
purpose was as part of some obsolete support for Emacs Lisp.
Can you try and find out what guile-gobject is using `nil' for? On
the one hand, the binding in libguile may have been hiding a bug in
guile-gobject; on the other hand, there may be a genuine need, in
which case we can look at putting it back.
In the meantime, a workaround should be:
(define nil 'nil)
Regards,
Neil