unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 2151@emacsbugs.donarmstrong.com
Subject: bug#2151: 23.0.90; Building the 23.0.90 pretest recompiles Lisp files
Date: Mon, 02 Feb 2009 22:42:43 +0200	[thread overview]
Message-ID: <utz7cvad8.fsf@gnu.org> (raw)
In-Reply-To: <jwvbptk7skr.fsf-monnier+emacsbugreports@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 2151@emacsbugs.donarmstrong.com,  emacs-pretest-bug@gnu.org
> Date: Mon, 02 Feb 2009 11:02:49 -0500
> 
> > It goes like this: since temacs is built, the last rule says to
> > produce bootstrap-emacs${EXEEXT}.  The new bootstrap-emacs then
> > triggers the 2 rules before it, which rebuild loaddefs.el and
> > recompile the Lisp files in ${lisp} and ${SOME_MACHINE_LISP}.
> 
> I think we have to live with this for now.

I feared you'd say that.  All I can say is that I think it's
fundamentally wrong to have Lisp files compile as part of the build
(Yes, I know we compile Leim files, presumably to conserve space in
the tarball, but I think that's wrong, too.)  The result is that a
successful build becomes less predictable, and we can no longer depend
on having the same good .elc files on all platforms.

(It is also a major headache for the DOS port, since lisp/Makefile
needs a Unixy shell, and I always avoided requiring that for building
an official release.)

> Getting make to understand the nature of the dependencies here is pretty
> tricky, so you can get it to work right for the tarball or you can get
> it to work right for the "cvs update" case, but it's pretty painful
> to get it to work right in both cases.

I think it shouldn't be too hard, and the ideas you suggested further
in your mail are my evidence.

> PS: Part of the problem, as far as I understand it, is that we need
> the .elc files to depend on bootstrap-emacs so as to tell `make' to
> build bootstrap-emacs when needed, but we don't actually need the .elc
> files to be newer than bootstrap-emacs (in some rare cases a newer
> bootstrap-emacs will compile the .el differently, but in general it's
> not the case).  But `make' doesn't have such a concept of a dependency
> that "needs to exist, but doesn't need to be older".

I don't think we need a bootstrap-emacs in a released version at all.
We could add some file to the tarball, generated at make-dist time, to
signal that bootstrap-emacs is not needed.  That file could actually
be named `bootstrap-emacs', which should resolve the problem nicely
(assuming we manage to have it older than the oldest .elc file).






  reply	other threads:[~2009-02-02 20:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02  6:03 bug#2151: 23.0.90; Building the 23.0.90 pretest recompiles Lisp files Eli Zaretskii
2009-02-02 16:02 ` Stefan Monnier
2009-02-02 20:42   ` Eli Zaretskii [this message]
2009-02-03 21:24     ` Stefan Monnier
2009-02-04  4:25       ` Eli Zaretskii
2009-02-04 19:51         ` Stefan Monnier
2009-02-21 16:10           ` Eli Zaretskii
2009-02-21 20:54             ` Stefan Monnier
2009-02-21 22:33               ` Eli Zaretskii
2009-02-21 22:49                 ` Stefan Monnier
2009-02-22  4:07                   ` Eli Zaretskii
2009-02-27 15:02                     ` Eli Zaretskii
2009-02-27 22:18                       ` Eli Zaretskii
2009-02-27 23:21                         ` Glenn Morris
2009-02-28 11:12                           ` Eli Zaretskii
2009-02-28  4:48                       ` Stefan Monnier
2009-02-28 10:41                         ` Eli Zaretskii
2009-02-28 22:06                           ` Stefan Monnier
2009-02-28 22:11                             ` Eli Zaretskii
2009-05-01 19:07                             ` Eli Zaretskii
2011-09-11 21:12                               ` Lars Magne Ingebrigtsen
2011-09-11 21:50                                 ` Chong Yidong
2014-06-27  0:42                                   ` Glenn Morris
2014-06-27  5:55                                     ` Eli Zaretskii
2009-02-22 18:19               ` Kevin Rodgers
2009-02-02 21:25   ` Magnus Henoch
2009-02-02 21:55     ` 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=utz7cvad8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=2151@emacsbugs.donarmstrong.com \
    --cc=monnier@iro.umontreal.ca \
    /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).