From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Add cedet/ede/shell.el to ELCFILES
Date: Sat, 17 Oct 2009 21:03:05 -0400 [thread overview]
Message-ID: <jwvfx9hy0r1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <yiskdhsx7k.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 17 Oct 2009 14:15:59 -0400")
>> This is with the current CVS:
>>
>> Maintainer warning: $(lisp)/cedet/ede/shell.el missing from $ELCFILES?
>> Compiling $(lisp)/cedet/ede/shell.el
>> Wrote $(lisp)/cedet/ede/shell.elc
> When you see such a warning (which is completely harmless, BTW), just
> run `make update-elclist' in the lisp directory, and commit
> Makefile.in.
BTW, if someone can come up with a way to get rid of `elcfiles' in
lisp/Makefile.in that would be very welcome. Its only purpose is to
allow parallel compilation of the .el files (which happens to be
unreliable anyway), so the pain it brings is fairly high compared to the
benefit. A solution that doesn't requires something like
`update-elcfiles' would be much preferred.
A solution that only works for GNU make would be acceptable, as long as
it doesn't break building with non-GNU makes.
Stefan
next prev parent reply other threads:[~2009-10-18 1:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 11:20 Add cedet/ede/shell.el to ELCFILES Eli Zaretskii
2009-10-17 14:32 ` Chong Yidong
2009-10-17 16:50 ` Eli Zaretskii
2009-10-17 18:12 ` Glenn Morris
2009-10-17 18:40 ` Glenn Morris
2009-10-17 23:41 ` Chong Yidong
2009-10-18 0:18 ` Glenn Morris
2009-10-18 0:35 ` Glenn Morris
2009-10-18 2:13 ` Chong Yidong
2009-10-18 2:14 ` Miles Bader
2009-10-18 8:15 ` Andreas Schwab
2009-10-17 18:15 ` Glenn Morris
2009-10-18 1:03 ` Stefan Monnier [this message]
2009-10-18 2:21 ` parallel bytecomp [was Re: Add cedet/ede/shell.el to ELCFILES] Glenn Morris
2009-10-18 6:01 ` Add cedet/ede/shell.el to ELCFILES Dan Nicolaescu
2009-10-18 14:31 ` Stefan Monnier
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=jwvfx9hy0r1.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.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.