unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Satyaki Das" <satyaki@theforce.stanford.edu>
Cc: eliz@gnu.org, Luc Teirlinck <teirllm@dms.auburn.edu>,
	monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Current CVS doesn't bootstrap
Date: Sat, 06 Nov 2004 18:42:49 -0800	[thread overview]
Message-ID: <5985.1099795369@trantor.xilinx.com> (raw)
In-Reply-To: <jeu0s2h1oh.fsf@sykes.suse.de>

Andreas Schwab <schwab@suse.de> writes:

> > Moreover, if a .el file is newer than the .elc file, then I _believe_
> > that the present version of make bootstrap _already_ recompiles
> > anyway.  (It is a long time ago that I did a `make bootstrap' without
> > a prior `make maintainer-clean', however.) 
> 
> But the problem is that the file to be compiled may require other files
> with a out-of-date elc files.

Yes, this is exactly the problem, especially if the code that you
are compiling have macros.  Then the old macros are used in the
new .elc files and all hell breaks loose.

We came across this in MH-E.  The solution that we came up with
was to add an advice to require to load the uncompiled file
instead of the .elc file which might be stale.  The code is in
lisp/mh-e/mh-acros.el.  For general use during emacs compilation,
I would vote for something a little more general where we check
the time-stamps of the .el and .elc file and load the .el if the
.elc is older.

Satyaki

  reply	other threads:[~2004-11-07  2:42 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06 11:25 Current CVS doesn't bootstrap Eli Zaretskii
2004-11-06 14:16 ` Andreas Schwab
2004-11-06 14:40 ` Andreas Schwab
2004-11-06 16:16   ` Eli Zaretskii
2004-11-06 22:48     ` Luc Teirlinck
2004-11-07  0:35       ` Andreas Schwab
2004-11-07  1:25         ` Luc Teirlinck
2004-11-07  1:45           ` Andreas Schwab
2004-11-07  2:42             ` Satyaki Das [this message]
2004-11-07  3:15               ` Luc Teirlinck
2004-11-07  1:33         ` Luc Teirlinck
2004-11-07  2:07           ` Andreas Schwab
2004-11-07 18:04         ` Richard Stallman
2004-11-07 18:55           ` Luc Teirlinck
2004-11-07 22:10             ` Luc Teirlinck
2004-11-08 16:58               ` Richard Stallman
2004-11-07 23:26             ` Kim F. Storm
2004-11-07 23:45               ` Luc Teirlinck
2004-11-08  7:27                 ` Eli Zaretskii
2004-11-09  0:50                   ` Luc Teirlinck
2004-11-07  5:07       ` Eli Zaretskii
2004-11-07 17:43         ` Luc Teirlinck
2004-11-07 18:25           ` Han Boetes
2004-11-07 19:05             ` Luc Teirlinck
2004-11-07 18:38           ` David Kastrup
2004-11-07 19:33             ` Luc Teirlinck
2004-11-07 19:42               ` David Kastrup
2004-11-07 20:21                 ` Luc Teirlinck
2004-11-08  0:15                   ` Robert J. Chassell
2004-11-07 20:34               ` Piet van Oostrum
2004-11-07 20:37               ` Piet van Oostrum
2004-11-07 21:09                 ` Luc Teirlinck
2004-11-07 21:20                 ` Luc Teirlinck
2004-11-07 22:28           ` Eli Zaretskii
2004-11-07 23:05             ` Luc Teirlinck
2004-11-08  1:32             ` Lennart Borgman
2004-11-08  8:22               ` Eli Zaretskii
2004-11-14 21:20                 ` Lennart Borgman
2004-11-08  2:03             ` Luc Teirlinck
2004-11-08  2:31               ` Luc Teirlinck
2004-11-08  7:20               ` Eli Zaretskii
2004-11-08 17:16             ` Drew Adams
2004-11-08 19:07               ` Stefan Monnier
2004-11-07 18:07         ` Luc Teirlinck
2004-11-07 18:47         ` Luc Teirlinck
  -- strict thread matches above, loose matches on Subject: below --
2005-02-14 11:12 Andreas Schwab
2005-02-14 12:51 ` Lute Kamstra
2005-02-14 13:36 ` Reiner Steib
2005-02-15 17:27   ` Richard Stallman
2005-02-15 20:56     ` Reiner Steib
2005-02-17 10:35       ` Richard Stallman
2005-02-15 17:27 ` Richard Stallman
2005-02-15 19:12   ` Lute Kamstra

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=5985.1099795369@trantor.xilinx.com \
    --to=satyaki@theforce.stanford.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=teirllm@dms.auburn.edu \
    /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).