From: Andreas Schwab <schwab@linux-m68k.org>
To: Barry OReilly <gundaetiapo@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: [RFC] Editing Lisp through changing indentation
Date: Fri, 30 Aug 2013 00:30:12 +0200 [thread overview]
Message-ID: <m2hae8jfkb.fsf@linux-m68k.org> (raw)
In-Reply-To: <CAFM41H3+ErPabtLqhNHBtZBu4p_2-K=cvgpPhnYkMG+OAsbqQg@mail.gmail.com> (Barry OReilly's message of "Thu, 29 Aug 2013 16:40:41 -0400")
Barry OReilly <gundaetiapo@gmail.com> writes:
> When I manually add the necessary -L flags (-L packages/trie/ -L
> packages/heap/ -L packages/tNFA/ -L packages/queue/) then I could byte
> compile with warnings. But how is it supposed to get the load paths?
Do you mean this?
diff --git a/GNUmakefile b/GNUmakefile
index 0fac72b..4ff3d31 100644
--- a/GNUmakefile
+++ b/GNUmakefile
@@ -127,7 +127,8 @@ elcs := $(call SET-diff, $(naive_elcs), $(patsubst %.el, %.elc, $(nbc_els)))
@$(EMACS) \
--eval "(setq package-directory-list '(\"$(abspath packages)\"))" \
--eval '(package-initialize)' \
- -L $(dir $@) -f batch-byte-compile $<
+ $(patsubst %, -L %, $(filter-out %/cl-lib, $(pkgs))) \
+ -f batch-byte-compile $<
.PHONY: elcs
elcs: $(elcs)
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-08-29 22:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 21:19 [RFC] Editing Lisp through changing indentation Barry OReilly
2013-08-29 0:14 ` Stefan Monnier
2013-08-29 19:50 ` Barry OReilly
2013-08-29 20:04 ` Stefan Monnier
2013-08-29 20:40 ` Barry OReilly
2013-08-29 22:14 ` Stefan Monnier
2013-08-29 22:30 ` Andreas Schwab [this message]
2013-08-29 22:39 ` Stefan Monnier
2013-08-29 22:49 ` Barry OReilly
2013-08-30 2:23 ` Stefan Monnier
2013-08-30 2:48 ` Barry OReilly
2013-08-30 3:24 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2013-07-19 3:23 Barry OReilly
2013-07-19 9:23 ` Thien-Thi Nguyen
2013-07-19 15:58 ` Drew Adams
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=m2hae8jfkb.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=gundaetiapo@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.