all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, "Jan D." <jan.h.d@swipnet.se>,
	joakim@verona.se, emacs-devel@gnu.org
Subject: Re: build broken: no defun org-float-time.  Who's guilty, and what does he propose?
Date: Mon, 7 Sep 2009 13:59:07 -0400	[thread overview]
Message-ID: <0C7A6FC6-085D-4B7F-9DC0-FF0493876153@raeburn.org> (raw)
In-Reply-To: <83ws4a3b49.fsf@gnu.org>

On Sep 7, 2009, at 13:42, Eli Zaretskii wrote:
>> From: "Jan D." <jan.h.d@swipnet.se>
>> Date: Mon, 7 Sep 2009 12:30:00 +0200
>> Cc: Alan Mackenzie <acm@muc.de>, "emacs-devel@gnu.org" <emacs-devel@gnu.org 
>> >
>>
>> A make that removed old .elc files and did bootstrap when needed is
>> the ideal solution. The second part is probably very hard.
>
> What we need IMO is a way to scan all the *.el files, look for
> `require', and generate Make dependencies between Lisp files.  Then
> this problem should be gone for good.
>
> Any takers?

I just spent part of the last couple of hours thinking over this  
problem too.  Other files could be autoloaded during compilation, and  
should be listed as dependencies too.

The byte compiler has rather a lot of information available while it's  
doing its job.  Perhaps it could look at the files that were loaded as  
part of the compilation, and generate a list of dependencies.  The  
byte compiler code itself, and files loaded via loadup.el, would still  
present a problem; a conservative approach would be to always list all  
of them as dependencies, though that would lead to excessive  
rebuilding still.

Ken




  reply	other threads:[~2009-09-07 17:59 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0C7A6FC6-085D-4B7F-9DC0-FF0493876153@raeburn.org \
    --to=raeburn@raeburn.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=joakim@verona.se \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.