From: Raphael Kubo da Costa <kubito@gmail.com>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: [PATCH] auth-source.el: Also load EIEIO when byte-compiling.
Date: Thu, 17 Feb 2011 01:05:53 -0200 [thread overview]
Message-ID: <87lj1fweb2.fsf@gmail.com> (raw)
In-Reply-To: <b4mbp2btlhb.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 17 Feb 2011 11:59:12 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> 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.
>
> Thanks. But I still get an error when loading auth-source.elc:
>
> Debugger entered--Lisp error: (void-variable auth-source-backend)
> byte-code("\304^H\305\306\307\310\311\312...
>
> A workaround is to remove auth-source.elc in the installation
> directory.
Weird, that is what I was getting before the commit. I'm on GNU Emacs
23.2.1 here.
Does it still happen if you run 'git clean -fdx && ./configure && make'?
Before the patch, make would show a lot of warnings related to
`defclass' not being defined when it was called in auth-source.el and it
was being byte-compiled. After the patch, the warnings disappear and I
can call (require 'auth-source) in the scratchb buffer without getting
the void-variable errors.
next prev parent reply other threads:[~2011-02-17 3:05 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 [this message]
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
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=87lj1fweb2.fsf@gmail.com \
--to=kubito@gmail.com \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.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).