unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, Ken Raeburn <raeburn@raeburn.org>,
	joakim@verona.se, jan.h.d@swipnet.se, emacs-devel@gnu.org
Subject: Re: build broken: no defun org-float-time.  Who's guilty, and what does he propose?
Date: Tue, 08 Sep 2009 13:01:21 -0400	[thread overview]
Message-ID: <jwviqft9yav.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83tyze34fd.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 07 Sep 2009 23:06:46 +0300")

>> Other files could be autoloaded during compilation, and should be
>> listed as dependencies too.
> We have `features' and `load-history' to help us.

It's doable, yes.  Note that just looking at the `require's and
`provide's will give you a graph with cycles.

> Files loaded by loadup.el are easily extracted by simple text
> scanning, and the byte compiler itself indeed _is_ a prerequisite for
> every other compilation.

Note that a basic hypothesis here, is that "make bootstrap" is not
a good solution, so any solution that ends recompiling similar amounts
of code is not good either.  But if you look in detail, you'll see that
only bootstrap does it really right: the byte-compiler is
a prerequisitie of all elc files, and the byte-compiler itself uses
potentially any code in loadup.el (and then some), so any change to
a preloaded file should fundamentally require recompiling all
Lisp files.  Anything short of that is an optimistic optimization.

> Btw, I don't understand what problem do you see with files preloaded
> by loadup.  They should simply be all prerequisites of temacs, and
> that's it, right?

Of temacs, no, but of `emacs' or `emacs-bootstrap', yes.
A recent case to ponder is the addition of define-obsolete-face-alias.
Maybe we can handle this one in the following way:

  When byte-compiling elc files with a preexisting emacs-bootstrap
  binary, re-load all the files that were preloaded but that have been
  changed since building emacs-bootstrap, before doing the actual
  recompilation (i.e. when starting emacs-bootstrap, check the
  load-history to see if any of those files have changed and reload them
  if needed).

Of course, this will bump into a few bugs at first, since some of the
preloaded files do not like to be re-loaded.


-- Stefan




  parent reply	other threads:[~2009-09-08 17:01 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07  9:28 build broken: no defun org-float-time. Who's guilty, and what does he propose? Alan Mackenzie
2009-09-07  9:47 ` Andreas Schwab
2009-09-07  9:52 ` joakim
2009-09-07 10:09   ` Lennart Borgman
2009-09-07 11:37     ` joakim
2009-09-07 10:30   ` Jan D.
2009-09-07 17:42     ` Eli Zaretskii
2009-09-07 17:59       ` Ken Raeburn
2009-09-07 18:32         ` Drew Adams
2009-09-07 18:42           ` Lennart Borgman
2009-09-07 19:22             ` Ken Raeburn
2009-09-07 19:03         ` Glenn Morris
2009-09-07 19:20           ` Drew Adams
2009-09-07 20:08           ` Eli Zaretskii
2009-09-07 21:43             ` more reliable `make' Glenn Morris
2009-09-08 16:46               ` Stefan Monnier
2009-09-10  6:28                 ` Glenn Morris
2009-09-10 13:37                   ` Stefan Monnier
2009-09-07 20:59           ` build broken: no defun org-float-time. Who's guilty, and what does he propose? joakim
2009-09-07 21:39             ` Glenn Morris
2009-09-07 21:55               ` joakim
2009-09-07 21:13           ` Alan Mackenzie
2009-09-08 16:48             ` Stefan Monnier
2009-09-08 18:17               ` build broken: no defun org-float-time. A workaround Alan Mackenzie
2009-09-08 19:08                 ` Ken Raeburn
2009-09-07 20:06         ` build broken: no defun org-float-time. Who's guilty, and what does he propose? Eli Zaretskii
2009-09-07 23:39           ` Ken Raeburn
2009-09-08  2:41             ` Stephen J. Turnbull
2009-09-08  3:20             ` Eli Zaretskii
2009-09-08  7:54               ` Ken Raeburn
2009-09-08 17:47                 ` Eli Zaretskii
2009-09-08 18:32                   ` Ken Raeburn
2009-09-08 17:01           ` Stefan Monnier [this message]
2009-09-08 17:51             ` Eli Zaretskii
2009-09-09  3:14               ` Stefan Monnier
2009-09-08  2:37       ` Stephen J. Turnbull
2009-09-08  3:14         ` Eli Zaretskii
2009-09-08 17:11   ` Stefan Monnier
2009-09-07 10:05 ` Miles Bader
2009-09-07 11:15   ` joakim
2009-09-07 13:35   ` Alan Mackenzie

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=jwviqft9yav.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=joakim@verona.se \
    --cc=raeburn@raeburn.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).