From: Pascal Bourguignon <pjb@informatimago.com>
Subject: problem with elisp compilator
Date: 04 Dec 2002 03:47:34 +0100 [thread overview]
Message-ID: <87smxeebzt.fsf@thalassa.informatimago.com> (raw)
I have the following problem while compiling some common-lisp sources
with emacs:
Compiling pjb-regexp.lisp ...
defining string=
While compiling pjb-re-string-match in file /home/pascal/src/common/lisp/common-lisp/pjb-regexp.lisp:
** string= called with 6 args, but requires 2
While compiling pjb-re-decorate-tree in file /home/pascal/src/common/lisp/common-lisp/pjb-regexp.lisp:
** member called with 4 args, but requires 2
Wrote /home/pascal/src/common/lisp/common-lisp/pjb-regexp.lisp.elc
Done
The compilator invocation is done as follow:
emacs -batch -q -l ../emacs/.emacs -l ../emacs/pjb-cl.el \
-f batch-byte-compile pjb-regexp.lisp
../emacs/.emacs contains (add-to-list 'load-path ... statements)
../emacs/pjb-cl.el requires 'cl and contain additionnal common-lisp definitions.
In particular, it contains:
(eval-when (compile load eval)
(mapc (lambda (sym) (fmakunbound sym))
'(
;; ...
string=
string<
;; ...
)
)
)
(message "defining string=")
(defun string= (string1 string2 &rest cl-keys)
;; &key :start1 :end1 :start2 :end2)
;; ...
)
(defadvice member
(around pjb-cl-member first (item alist &rest cl-keys) activate)
;;...
)
(ad-activate 'member)
The message "defining string=" shows that pjb-cl.el is loaded at the
beginning of the compilation of pjb-regexp.lisp, but then it seems
that the compilator does not take into account definitions in this
file neither of a new string= definition or of an advice to an
existing primitive.
Doesn't it looks like a bug? What can I do about it?
--
__Pascal_Bourguignon__ http://www.informatimago.com/
----------------------------------------------------------------------
There is no worse tyranny than to force a man to pay for what he does not
want merely because you think it would be good for him. -- Robert Heinlein
next reply other threads:[~2002-12-04 2:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 2:47 Pascal Bourguignon [this message]
2002-12-05 16:54 ` problem with elisp compilator Kevin Rodgers
2002-12-06 22:50 ` Pascal Bourguignon
2002-12-07 14:01 ` Kai Großjohann
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=87smxeebzt.fsf@thalassa.informatimago.com \
--to=pjb@informatimago.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.