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: Wed, 04 Feb 2009 06:25:48 +0200 [thread overview]
Message-ID: <u4ozavneb.fsf@gnu.org> (raw)
In-Reply-To: <jwvvdrrp6ax.fsf-monnier+emacsbugreports@gnu.org>
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: 2151@emacsbugs.donarmstrong.com
> Date: Tue, 03 Feb 2009 16:24:54 -0500
>
> >> 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.
>
> Have you tried it? It seems to work OK for the "checkout from CVS"
> case, so maybe it's a good solution.
Which one? you suggested more than one, I think.
> > 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).
>
> 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.
> 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.
I will give this a try when I have time.
next prev parent reply other threads:[~2009-02-04 4:25 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 [this message]
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=u4ozavneb.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).