Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: asjo@koldfront.dk (Adam Sjøgren)
Cc: ding@gnus.org
Subject: Re: XEmacs builds failing - gnus-spec.el
Date: Mon, 20 May 2013 09:39:08 +0200	[thread overview]
Message-ID: <871u92yuar.fsf@randomsample.de> (raw)
In-Reply-To: <87li7asg2y.fsf@topper.koldfront.dk> ("Adam \=\?iso-8859-1\?Q\?Sj\?\= \=\?iso-8859-1\?Q\?\=F8gren\=22's\?\= message of "Mon, 20 May 2013 01:30:29 +0200")

Adam Sjøgren writes:
> asjo@koldfront.dk (Adam Sjøgren) writes:
>
>> I wonder if simply changing that to (= delim ?\u00AB)) would do the
>> trick.
>
> That made the 21.5 buildbot go green:
>
>  * http://www.randomsample.de:4456/waterfall
>
> Cool!

Thanks for fixing this. The XEmacs on the Buildbot is indeed build with
default specs, i.e., without Mule.

> Now the 21.4 fails somewhere after yenc.el instead of on gnus-spec.el,
> so that's progress as well:
>
>  * http://www.randomsample.de:4456/builders/xemacs21.4-linux/builds/963/steps/compile/logs/stdio

No, it fails before with

While compiling gnus-parse-complex-format in file /var/lib/buildbot/slaves/debian/build-xemacs21.4/build/lisp/gnus-spec.el:
  !! error (("reference to free variable 00AB"))

XEmacs 21.4 behaves strangely with the Buildbot. If there is an error,
it stalls at the end until the Buildbot kills the process; yenc.el is
simply the last file that is compiled. It works fine on the command
line, so I've no idea why it does not work when called from the
Buildbot.

-David



  reply	other threads:[~2013-05-20  7:39 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
2013-05-19 22:13     ` Adam Sjøgren
2013-05-19 23:30       ` Adam Sjøgren
2013-05-20  7:39         ` David Engster [this message]
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=871u92yuar.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --cc=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).