From: Jason Rumney <jasonr@gnu.org>
Cc: Luc Teirlinck <teirllm@dms.auburn.edu>,
ich@Frank-Schmitt.net, emacs-devel@gnu.org
Subject: Re: make bootstrap on CVS head fails
Date: Mon, 06 Sep 2004 16:26:10 +0100 [thread overview]
Message-ID: <413C8192.9080307@gnu.org> (raw)
In-Reply-To: <m3656rsa4b.fsf@kfs-l.imdomain.dk>
[-- Attachment #1.1: Type: text/plain, Size: 764 bytes --]
Kim F. Storm wrote:
>Luc Teirlinck <teirllm@dms.auburn.edu> writes:
>
>
>>Frank-Schmitt wrote:
>>
>> If this is necessary before a bootstrap, why doesn't bootstrap depend on
>> maintainer-clean?
>>
>>It used to, but that was changed to make bootstrapping run faster at
>>the expense of an occasional failure. (Personally, I believe that
>>change was a mistake.)
>>
>>
>
>I agree that bootstrap should do maintainer-clean.
>
>
I wasn't aware of the change so I was a bit confused by the original
report. If you want to compile faster, use "make recompile" to recompile
the .elc files followed by a normal "make".
The cases where recompile is not enough and bootstrap is really
necessary are probably the same cases of "occasional failure" above.
[-- Attachment #1.2: Type: text/html, Size: 1261 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2004-09-06 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 12:09 make bootstrap on CVS head fails Frank Schmitt
2004-09-06 13:43 ` Sébastien Kirche
2004-09-07 3:43 ` Richard Stallman
2004-09-07 8:51 ` Sébastien Kirche
2004-09-06 14:16 ` Luc Teirlinck
2004-09-06 14:31 ` Frank Schmitt
2004-09-06 15:04 ` Luc Teirlinck
2004-09-06 15:14 ` Kim F. Storm
2004-09-06 15:26 ` Jason Rumney [this message]
2004-09-09 14:32 ` Piet van Oostrum
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=413C8192.9080307@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ich@Frank-Schmitt.net \
--cc=teirllm@dms.auburn.edu \
/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.