From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Error compiling spam.el
Date: Tue, 22 Oct 2002 12:42:24 +0900 [thread overview]
Message-ID: <yotlk7kbi1gf.fsf@jpl.org> (raw)
In-Reply-To: <yotlsmyzi3ae.fsf@jpl.org>
>>>>> In <yotlsmyzi3ae.fsf@jpl.org>
>>>>> Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> I apologize to all. It is my fault. Could you use the most
> recent Gnus CVS?
>>>| In toplevel form:
>>>| spam.el:49:41:Error: Recursive `require' for feature `bbdb'
Oops. My last chage didn't fix the problem as follows:
% emacs -batch -q -no-site-file -eval\
'(progn (autoload (quote bbdb-records) "bbdb-com") (bbdb-records))'
=> Variable binding depth exceeds max-specpdl-size
It is equal when not loading bbdb.elc before spam.elc. I will
consider how to fix it...
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2002-10-22 3:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 17:44 Henrik Enberg
2002-10-22 2:51 ` Ted Zlatanov
2002-10-22 3:02 ` Katsumi Yamaoka
2002-10-22 3:42 ` Katsumi Yamaoka [this message]
2002-10-22 5:04 ` Katsumi Yamaoka
2002-10-22 5:09 ` Henrik Enberg
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=yotlk7kbi1gf.fsf@jpl.org \
--to=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).