all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Add cedet/ede/shell.el to ELCFILES
Date: Sat, 17 Oct 2009 18:50:54 +0200	[thread overview]
Message-ID: <83r5t2ge1d.fsf@gnu.org> (raw)
In-Reply-To: <87iqeet7kt.fsf@stupidchicken.com>

> From: Chong Yidong <cyd@stupidchicken.com>
> Cc: emacs-devel@gnu.org
> Date: Sat, 17 Oct 2009 10:32:02 -0400
> 
> One reason I missed this error is that each time I compile, I get the
> errors about the unicode files, e.g.
> 
> Maintainer warning: $(lisp)/international/uni-bidi.el missing from $ELCFILES?
> Compiling /home/cyd/emacs/lisp/international/uni-bidi.el
> Maintainer warning: $(lisp)/international/uni-category.el missing from $ELCFILES?
> Compiling /home/cyd/emacs/lisp/international/uni-category.el

Is this during bootstrap?  I don't think I see it during a regular
build.  And since these files are modified only very rarely, they
shouldn't present a problem, unless I'm missing something.

Btw, there are 85 files under lisp/ that have "no-byte-compile: t", so
why these few are special?




  reply	other threads:[~2009-10-17 16:50 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 [this message]
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
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=83r5t2ge1d.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@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.