From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [PATCH] auth-source.el: Also load EIEIO when byte-compiling.
Date: Wed, 16 Feb 2011 21:22:30 -0600 [thread overview]
Message-ID: <87r5b7ibux.fsf@lifelogs.com> (raw)
In-Reply-To: <b4mbp2btlhb.fsf@jpl.org>
On Thu, 17 Feb 2011 11:59:12 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote:
KY> Raphael Kubo da Costa <kubito@gmail.com> wrote:
>> Commit 4a0aa92 moved (require 'eieio) to an `or', and the
>> byte-compiler only loads top-level `require' calls, which resulted in
>> problems when the byte-compiler tried to evaluate the `defclass'
>> macro.
>> The fallback loading code has also been changed -- there was a single
>> condition being checked, and if it evaluated to t the `load' call was
>> always made.
KY> Thanks. But I still get an error when loading auth-source.elc:
KY> Debugger entered--Lisp error: (void-variable auth-source-backend)
KY> byte-code("\304^H\305\306\307\310\311\312...
KY> A workaround is to remove auth-source.elc in the installation
KY> directory.
It works for me, but I did "make clean". Do you mean people will get
that Lisp error randomly? Or when they don't do "make clean"? I don't
know dgnushack.el or much of the byte-compilation arcana, so any help is
greatly appreciated.
Raphael, thanks for the patch. I was in a hurry and didn't look carefully.
Ted
prev parent reply other threads:[~2011-02-17 3:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 1:47 Raphael Kubo da Costa
2011-02-17 2:59 ` Katsumi Yamaoka
2011-02-17 3:05 ` Raphael Kubo da Costa
2011-02-17 3:55 ` Katsumi Yamaoka
2011-02-17 4:34 ` Raphael Kubo da Costa
2011-02-17 5:00 ` Katsumi Yamaoka
2011-02-17 17:02 ` Ted Zlatanov
2011-02-17 3:22 ` Ted Zlatanov [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=87r5b7ibux.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).