From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Ulrich Mueller <ulm@gentoo.org>, 8302@debbugs.gnu.org
Subject: bug#8302: 23.3; Parallel make: some *.el files are byte-compiled twice
Date: Thu, 19 May 2011 02:15:08 -0400 [thread overview]
Message-ID: <tufwobrzbn.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvpqnf1lkr.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 18 May 2011 23:18:12 -0300")
Stefan Monnier wrote:
> If it works correctly, that's great.
It works for me... Let's see if it works for everyone else.
> Eliminating the shortlisp-vs-lisp duplication would be the next
> logical step.
Still can't see how to do that. Hopefully it's a bit easier to keep
up-to-date now it is almost a literal copy of $lisp.
Something clever with xargs?
Or, $lisp could be in a separate lisp.mk file that configure could
include into src/Makefile, and then for DOC use something like:
$(libsrc)/make-docfile -a $(etc)/DOC \
-d $(srcdir) `sed 's|$(lispsource)|../lisp|' $(srcdir)/lisp.mk`
?
next prev parent reply other threads:[~2011-05-19 6:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 20:26 bug#8302: 23.3; Parallel make: some *.el files are byte-compiled twice Ulrich Mueller
2011-05-19 1:35 ` Glenn Morris
2011-05-19 2:18 ` Stefan Monnier
2011-05-19 6:15 ` Glenn Morris [this message]
2011-05-19 12:27 ` Dan Nicolaescu
2011-05-20 0:51 ` Glenn Morris
2011-05-24 16:46 ` Dan Nicolaescu
2011-05-24 17:31 ` bug#7397: " Glenn Morris
2011-05-25 3:30 ` Glenn Morris
2011-05-25 13:52 ` Stefan Monnier
2010-11-14 9:01 ` bug#7397: make-docfile should support the @FILE command line option Dan Nicolaescu
2010-11-14 9:31 ` Eli Zaretskii
2010-11-14 17:01 ` Dan Nicolaescu
2011-05-25 20:56 ` bug#7397: bug#8302: 23.3; Parallel make: some *.el files are byte-compiled twice Glenn Morris
2011-05-25 23:56 ` Stefan Monnier
2011-07-09 19:03 ` bug#7397: make-docfile should support the @FILE command line option Glenn Morris
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=tufwobrzbn.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=8302@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=ulm@gentoo.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.
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.