From: Neil Jerram <neil@ossau.uklinux.net>
To: rm@fabula.de
Cc: "Neil W. Van Dyke" <nwv@neilvandyke.org>,
guile-gtk@sourceware.cygnus.com, guile-user@gnu.org,
guile-devel@gnu.org
Subject: Re: Taming the beast [was: Re: guile-gobject 0.3.0 Released]
Date: Fri, 08 Feb 2002 03:03:00 -0000 [thread overview]
Message-ID: <m3it988cf7.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <20020206133521.GA3525@www>
>>>>> "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
prev parent reply other threads:[~2002-02-08 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 11:29 guile-gobject 0.3.0 Released Ariel Rios
2002-01-29 19:01 ` Eric Gillespie
2002-01-29 20:39 ` Ariel Rios
2002-02-04 15:05 ` (Was: guile-gobject 0.3.0 Released) Neil W. Van Dyke
2002-02-04 21:30 ` Ariel Rios
2002-02-04 14:15 ` guile-gobject 0.3.0 Released Neil W. Van Dyke
2002-02-06 5:24 ` Taming the beast [was: Re: guile-gobject 0.3.0 Released] rm
2002-02-08 3:03 ` Neil Jerram [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3it988cf7.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=guile-user@gnu.org \
--cc=nwv@neilvandyke.org \
--cc=rm@fabula.de \
/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).