From: Achim Gratz <Stromeko@nexgo.de>
Subject: Re: Problem with make and autoloads
Date: Thu, 02 Jun 2011 22:49:42 +0200 [thread overview]
Message-ID: <87vcwo3qmx.fsf@Rainer.invalid> (raw)
Matt Lundin <firstname.lastname@example.org> writes:
> They are the default values (i.e., I have not changed anything).
> Note: I do not run "make install". My normal routine is to run "make
> clean && make".
Yes, I noted this, I was just poking around to see where the build
process might pick up that extra "lisp/" in org-install. On another
note, where is that org-install located? Could it be you have maybe two
of them and Emacs picks up the wrong one? The end of the make should
look something like this (watch the linewraps:
emacs -batch -q -no-site-file -eval "(setq load-path (cons (expand-file-name \"./lisp/\") (cons \"<<$lispdir>>\" load-path)))" --eval "(require 'autoload)" \
--eval '(find-file "org-install.el")' \
--eval '(erase-buffer)' \
--eval '(mapc (lambda (x) (generate-file-autoloads (symbol-name x))) (quote (lisp/org.el <<...>> lisp/ob-scheme.el)))' \
--eval '(insert "\n(provide (quote org-install))\n")' \
Generating autoloads for lisp/org.el...
Saving file <<.>>/org-install.el...
mv org-install.el lisp
^^^maybe the file is not moved at all or can't be deleted?
emacs -batch -q -no-site-file -eval "(setq load-path (cons
(expand-file-name \"./lisp/\") (cons \"<<$lispdir>>\" load-path)))" -f batch-byte-compile lisp/org-install.el
If this does not happen after you've removed both org-install.el and
org-install.elc and then do another make, then somethings is very wrong.
My guess is that you have a stray org-install.el in <<.>> (make clean
probably should remove it both here and in ./lisp, but doesn't).
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
next prev parent reply other threads:[~2011-06-02 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 16:56 Problem with make and autoloads Matt Lundin
2011-05-27 17:32 ` Achim Gratz
2011-06-02 0:46 ` Matt Lundin
2011-06-02 20:49 ` Achim Gratz [this message]
2011-05-30 6:40 ` suvayu ali
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 public inbox
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).