unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 2151@emacsbugs.donarmstrong.com
Subject: bug#2151: 23.0.90; Building the 23.0.90 pretest recompiles Lisp files
Date: Sat, 21 Feb 2009 15:54:01 -0500	[thread overview]
Message-ID: <jwveixrjz8p.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <uk57ju5x4.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 21 Feb 2009 18:10:47 +0200")

>> >> > 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).
>> >> Maybe we can get that to work, but it sounds terribly hackish.
>> > Why hackish? many distributions have or create such time-stamp files,
>> > for Make's sake.
>> 
>> I guess it depends on the details.

> After thinking some more about this, I don't see any easy and safe
> solution besides adding a "bootstrap-emacs" file to the tarball.
> Maybe in future releases we will be able to find a better way, but for
> now this is the only one that's safe.

> I will do that if you agree.

I'd rather not if the patch I suggested works.  Does it?

> In any case, it sounds wrong to me to have the distribution biased in
> favor of people who build Emacs out of CVS.

My guess is that many more people build from CVS than from the release
tarball.  Most users of the release will use a precompiled package.
So I care much more about building from CVS than building from
a tarball.  Also I care more about the build being reliable and
maintainable, than about it being optimal in all circumstances, so if
building from the tarball does a bit of extra work, I don't really mind
as long as it makes maintenance easier.
I do think the patch I proposed fixes the problem and doesn't make the
code significantly more hairy, so I'm willing to install it.  I've been
using it ever since I sent it and it seems to work fine (tho
I basically never boostrap anyway), but I'd like confirmation that it
fixes your problem before installing it.

>> >> Also, I'd like to make sure that if some wants to change some .el files
>> >> and then recompile, it still works correctly.
>> > It will, I think, because we can copy emacs to bootstrap-emacs at the
>> > end of the build.
>> What if they edit .el files before building a first `emacs'?
> We could arrange for byte-recompile-directory at the end of the build,
> if that is a real-life use-case.

That wouldn't help: the problem is that such a change would trigger
recompilation of the .elc file, which in turn will run your dummy
bootstrap-emacs, at which point the build will presumably fail.


        Stefan






  reply	other threads:[~2009-02-21 20:54 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
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 [this message]
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=jwveixrjz8p.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=2151@emacsbugs.donarmstrong.com \
    --cc=eliz@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 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).