From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: XEmacs builds failing - gnus-spec.el
Date: Sun, 19 May 2013 23:58:14 +0200 [thread overview]
Message-ID: <8761yetyx5.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <5277.1368999929@rawbw.com>
Hi Mike!
Mike Kupfer <mike.kupfer@xemacs.org> writes:
>> Compiling /var/lib/buildbot/slaves/debian/build-xemacs21.5/build/lisp/gnus-spec.el...
>> While compiling gnus-parse-complex-format in file /var/lib/buildbot/slaves/debian/build-xemacs21.5/build/lisp/gnus-spec.el:
>> !! error (("reference to free variable �"))
> I expect this has something to do with the guillemet quote, maybe the
> comparison with ``delim'':
>
> (= delim ?\«))
Ok - do you have any suggestions for how to fix it?
(I wanted to tinker with it myself, but failing to make it fail made me
write here instead :-))
> Were the involved XEmacsen (the buildbot one and yours) configured with
> --with-mule? IIRC, it's not the default.
Good question. I don't know about the buildbot, I think my local one
was, because the binary is called "xemacs-21.5-b31-mule".
So if the buildbot's binary is non-mule, it might be a problem only for
non-mule XEmacsen...
o o o
Oh, I just realized that I also have an XEmacs 21.4 installed (Debian
package). "make EMACS=/usr/bin/xemacs-21.4.22-mule" in a fresh Gnus
checkout fails like this:
Generating autoloads for lisp/gnus-spec.el...
Unbalanced parentheses
xemacs exiting
If I roll back the changes to gnus-spec.el, it completes the 'make'
without error.
Interesting, now I have something to tinker with, even though it only is
the old version.
Best regards,
Adam
--
"Hur långt man än har kommit Adam Sjøgren
är det alltid längre kvar" asjo@koldfront.dk
next prev parent reply other threads:[~2013-05-19 21:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 19:23 Adam Sjøgren
2013-05-19 21:45 ` Mike Kupfer
2013-05-19 21:58 ` Adam Sjøgren [this message]
2013-05-19 22:13 ` Adam Sjøgren
2013-05-19 23:30 ` Adam Sjøgren
2013-05-20 7:39 ` David Engster
2013-05-20 16:01 ` Adam Sjøgren
2013-05-20 16:36 ` Adam Sjøgren
2013-05-20 23:55 ` Katsumi Yamaoka
2013-05-21 21:01 ` Adam Sjøgren
2013-05-21 23:39 ` Katsumi Yamaoka
2013-05-22 2:58 ` Mike Kupfer
2013-05-22 5:45 ` Katsumi Yamaoka
2013-05-28 0:22 ` Mike Kupfer
2013-05-31 12:07 ` Mats Lidell
2013-05-22 20:18 ` Adam Sjøgren
2013-05-22 20:28 ` Adam Sjøgren
2013-05-22 20:36 ` David Engster
2013-05-28 0:43 ` Mike Kupfer
2013-06-01 22:04 ` XEmacs hash table representation (was XEmacs builds failing - gnus-spec.el) Mike Kupfer
2013-06-02 8:59 ` David Engster
2013-06-02 16:22 ` Mike Kupfer
2013-06-06 14:46 ` Ted Zlatanov
2013-06-06 16:06 ` Mike Kupfer
2013-05-22 3:02 ` XEmacs builds failing - gnus-spec.el Mike Kupfer
2013-05-22 20:25 ` David Engster
2013-05-28 0:25 ` Mike Kupfer
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=8761yetyx5.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).