unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, bug-cc-mode@gnu.org, henrik.enberg@telia.com,
	romain@orebokech.com, mast@lysator.liu.se, emacs-devel@gnu.org
Subject: Re: Release of CC Mode 5.31
Date: Wed, 07 Dec 2005 20:48:58 +0200	[thread overview]
Message-ID: <ud5k8lp45.fsf@gnu.org> (raw)
In-Reply-To: <E1Ek2ky-0007J2-78@fencepost.gnu.org> (rms@gnu.org)

> From: "Richard M. Stallman" <rms@gnu.org>
> CC: acm@muc.de, bug-cc-mode@gnu.org, henrik.enberg@telia.com,
> 	romain@orebokech.com, mast@lysator.liu.se, emacs-devel@gnu.org
> Date: Wed, 07 Dec 2005 12:07:04 -0500
> 
>     After I saw the problem, but before I reported it, I recompiled all
>     the cc-*.el files, by "make recompile".  Perhaps that command does not
>     compile the files in the order you mention.  It would be nice if it
>     did that automatically.
> 
> There is no Emacs feature to control order of compilation,
> so there would be no easy way to make that automatic.

I thought about some Make magic, like making some of the *.elc files
dependent on some other *.elc files which need to be compiled first.
(We already have COMPILE_FIRST files that work around similar
problems.)  Is there any reason why this wouldn't work?


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click


  parent reply	other threads:[~2005-12-07 18:48 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 12:20 Release of CC Mode 5.31 Alan Mackenzie
2005-12-02 17:15 ` Henrik Enberg
2005-12-02 20:42   ` Alan Mackenzie
2005-12-03 15:58     ` Richard M. Stallman
2005-12-03 16:15       ` Alan Mackenzie
2005-12-03 11:48   ` Alan Mackenzie
2005-12-03 12:40     ` Romain Francoise
2005-12-03 15:33     ` Henrik Enberg
2005-12-04  3:08     ` Richard M. Stallman
2005-12-05 16:48       ` Alan Mackenzie
2005-12-06 16:43         ` Richard M. Stallman
2005-12-04 19:40     ` Eli Zaretskii
2005-12-04 19:45       ` Romain Francoise
2005-12-06 12:11       ` Alan Mackenzie
2005-12-06 20:33         ` Eli Zaretskii
2005-12-07 17:07           ` Richard M. Stallman
2005-12-07 18:14             ` Alan Mackenzie
2005-12-08  4:53               ` Richard M. Stallman
2005-12-07 18:48             ` Eli Zaretskii [this message]
2005-12-07 19:51               ` Stefan Monnier
2005-12-07 22:41                 ` Eli Zaretskii
2005-12-08  4:54                 ` Richard M. Stallman
2005-12-08  4:53               ` Richard M. Stallman
2005-12-08 16:43                 ` Stefan Monnier
2005-12-08 19:47                   ` Eli Zaretskii
2005-12-08 22:24                     ` Stefan Monnier
2005-12-08 23:04                       ` Kim F. Storm
2005-12-08 23:46                         ` Stefan Monnier
2005-12-09 12:30                           ` Eli Zaretskii
2005-12-09 14:42                             ` Stefan Monnier
2005-12-10  4:13                               ` Richard M. Stallman
2005-12-09 12:35                       ` Eli Zaretskii
2005-12-09 14:42                         ` Stefan Monnier
2005-12-09 15:02                       ` Richard M. Stallman
2005-12-08 23:32                   ` Andreas Schwab
2005-12-09  1:42                   ` Richard M. Stallman
2005-12-08 19:29                 ` Eli Zaretskii
2005-12-09  1:43                   ` Richard M. Stallman
2005-12-06 10:32 ` Romain Francoise
2005-12-06 13:09   ` Alan Mackenzie
2005-12-06 13:46   ` Masatake YAMATO
2005-12-06 20:34   ` Eli Zaretskii
2005-12-06 20:49     ` Romain Francoise
2005-12-06 21:04       ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ud5k8lp45.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=henrik.enberg@telia.com \
    --cc=mast@lysator.liu.se \
    --cc=romain@orebokech.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).