From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Glenn Morris <rgm@gnu.org>,
emacs-devel@gnu.org, monnier@iro.umontreal.ca, acm@muc.de
Subject: Re: Build-time dependencies
Date: Sun, 08 Jun 2008 21:31:43 +0200 [thread overview]
Message-ID: <85mylv7mg0.fsf@lola.goethe.zz> (raw)
In-Reply-To: <uhcc3lofc.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 08 Jun 2008 22:25:11 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Glenn Morris <rgm@gnu.org>
>> Cc: Alan Mackenzie <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>> Date: Sun, 08 Jun 2008 15:03:07 -0400
>>
>> Stefan Monnier wrote:
>>
>> > I think it should be easy to generate the dependencies from bytecomp.el
>> > (just record macros as we expand them, and then try and figure out
>> > which file they come from). This way they could be kept uptodate
>> > 100% automatically.
>>
>> What exactly is the point of doing this supposed to be?
>> To make non-bootstrap builds more reliable?
>
> To make dependencies between Lips files explicit in lisp/Makefile.in,
> and thus causing Make to compile Lisp files in the right order. Right
> now, whenever some Lisp files change, I frequently need to "make
> recompile" several times, sometimes removing stale *.elc files
> manually, until it finally succeeds, because it basically compiles
> them in a random order.
Personally, I would appreciate it if we could get of the bootstrap
target altogether, and when Emacs chose to do a bootstrap on "make"
whenever things could require it.
Similar with the "clean" target. Having special targets that will _not_
bootstrap even when it _could_ be necessary in order to make debugging
faster/easier is nice.
But I think without extra measures, it would be nice if "make" did
everything that might be required. The combination of "recompile" and
"cvs-update" and "bootstrap" and "whatever-clean" in what ever
directories that one has to try whenever something looks like not
working:
That is not really the idea behind using make.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2008-06-08 19:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 15:59 Yet another bootstrap failure: Required feature `esh-groups' was not provided Alan Mackenzie
2008-06-06 17:22 ` Glenn Morris
2008-06-06 18:23 ` Dan Nicolaescu
2008-06-06 19:27 ` Stefan Monnier
2008-06-06 20:35 ` Alan Mackenzie
2008-06-06 20:41 ` Eli Zaretskii
2008-06-07 2:53 ` Glenn Morris
2008-06-07 9:07 ` Alan Mackenzie
2008-06-07 19:49 ` Glenn Morris
2008-06-07 9:50 ` Alan Mackenzie
2008-06-07 12:19 ` Eli Zaretskii
2008-06-07 20:08 ` Alan Mackenzie
2008-06-07 22:17 ` Stephen J. Turnbull
2008-06-07 22:29 ` Romain Francoise
2008-06-08 2:58 ` Stefan Monnier
2008-06-08 2:56 ` Build-time dependencies Stefan Monnier
2008-06-08 19:03 ` Glenn Morris
2008-06-08 19:25 ` Eli Zaretskii
2008-06-08 19:31 ` David Kastrup [this message]
2008-06-09 1:44 ` Glenn Morris
2008-06-09 1:49 ` Glenn Morris
2008-06-09 8:26 ` Eli Zaretskii
2008-06-09 15:32 ` Ted Zlatanov
2008-06-09 15:32 ` David Kastrup
2008-06-09 10:30 ` Robert J. Chassell
2008-06-09 17:22 ` Richard M Stallman
2008-06-09 18:15 ` Glenn Morris
2008-06-09 19:47 ` Miles Bader
2008-06-09 19:53 ` Glenn Morris
2008-06-10 18:22 ` Ted Zlatanov
2008-06-10 18:54 ` Stefan Monnier
2008-06-09 4:37 ` Stephen J. Turnbull
2008-06-09 1:51 ` Stefan Monnier
2008-06-09 16:41 ` Alan Mackenzie
2008-06-07 22:32 ` Yet another bootstrap failure: Required feature `esh-groups' was not provided Stephen J. Turnbull
2008-06-07 2:51 ` Glenn Morris
2008-06-07 8:58 ` Alan Mackenzie
2008-06-06 23:51 ` Vinicius Jose Latorre
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=85mylv7mg0.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@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).