From: "Sébastien Kirche" <sebastien.kirche.no@spam.free.fr.invalid>
Subject: Re: eudc fails with bbdb
Date: Fri, 15 Apr 2005 18:42:24 +0200 [thread overview]
Message-ID: <85wtr4dma7.fsf@obelix.seki.fr> (raw)
In-Reply-To: 873bts11mx.fsf-monnier+gnu.emacs.help@gnu.org
Le 15 avr 2005, Stefan Monnier a formulé :
> > > > I have tried to byte-recompile the bbdb lisp files, but it keeps
> > > > on failing withe same "invalid-function".
> > > Since the error is in eudc-bbdb-extract-phones, recompiling bbdb
> > > won't help. How could I have explained it better?
>
> > Sorry, i did not understand the problem in that way : i though it
> > was due to bbdb.
>
> I figured that much, which is why I ask (again): how could I have
> explained it better?
I am sorry Stefan, the problem seems to be there between my chair and my
keyboard : I am not that familiar with lisp debugging and I focused my
attention
- to your other sentence «Such an error is almost invariably due to a
miscompiled file»
- and to the fact that the last function listed by the backtrace is
bbdb-record-phones that is part of bbdb.
That's why I kept on compiling bbdb.el while you were pointing
eudc-bbdb-extract-phones to me.
> > by a simple (require 'bbdb) or (require 'bbdb nil t) ?
>
> It should be just (require 'bbdb), I guess, except that BBDB is not
> part of Emacs, so we can't properly compile eudcb-bbdb.el in Emacs.
> I.e. another solution is required.
>
> > As using eudcb-bbdb implies the use of bbdb...
>
> But it gets compiled long before knowing whether you're going to ever
> use it.
>
> > Should it be forwarded to emacs-devel ? What do you think of it ?
>
> Of course.
I will send such a report in few.
> (Re-)Read the INSTALL.CVS file.
Are you talking about that part (otherwise i don't understand your
remark) ?
,----
| Occasionally the file "lisp/loaddefs.el" will need be updated to reflect
| new autoloaded functions. If you see errors about undefined lisp
| functions during compilation, that may be the reason. Another symptom
| may be an error saying that "loaddefs.el" could not be found; this is
| due to a change in the way loaddefs.el was handled in CVS, and should
| only happen once, for users that are updating old CVS trees.
|
| To update loaddefs.el, do:
|
| $ cd lisp
| $ make autoloads EMACS=../src/emacs
|
| If either of above procedures fails, try "make bootstrap".
`----
But I actually don't know if loaddefs.el is concerned by that problem.
Anyway, it was not obvious to me that installing a package like bbdb
would need to modify already installed files other than just usual
.emacs/.gnus config files.
--
Sébastien Kirche
next prev parent reply other threads:[~2005-04-15 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 11:26 eudc fails with bbdb Sébastien Kirche
2005-04-14 14:40 ` Stefan Monnier
2005-04-14 15:47 ` Sébastien Kirche
2005-04-15 13:28 ` Stefan Monnier
2005-04-15 14:57 ` Sébastien Kirche
2005-04-15 15:53 ` Stefan Monnier
2005-04-15 16:42 ` Sébastien Kirche [this message]
2005-04-16 4:11 ` Stefan Monnier
2005-04-14 15:38 ` Kevin Rodgers
[not found] ` <mailman.1508.1113493483.2895.help-gnu-emacs@gnu.org>
2005-04-14 15:56 ` Sébastien Kirche
2005-04-14 22:33 ` Kevin Rodgers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85wtr4dma7.fsf@obelix.seki.fr \
--to=sebastien.kirche.no@spam.free.fr.invalid \
--cc=sebastien.kirche@free.fr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).