all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: john_owens@yahoo.com, xsteve@riic.at, emacs-devel@gnu.org
Subject: Re: appears CVS build is broken (tty-supports-face-attributes-p)?
Date: Wed, 30 Jun 2004 22:38:59 -0500 (CDT)	[thread overview]
Message-ID: <200407010338.i613cxZ25774@raven.dms.auburn.edu> (raw)
In-Reply-To: <buo3c4cwjw7.fsf@mctpc71.ucom.lsi.nec.co.jp> (message from Miles Bader on Thu, 01 Jul 2004 11:17:44 +0900)

Miles Bader wrote:

   BTW, usually it's sufficient to do `make -C lisp recompile', and of
   course it's much faster.  So a generally good strategy after updating is
   to do that followed by a normal make, and if it fails in a suspicious
   way, then try make maintainer-clean + make bootstrap.

In practice, people are going to do what we _ask_ then to do in
INSTALL.CVS:

    Normally, it is not necessary to use "make bootstrap" after every CVS
    update.  Unless there are problems, we suggest the following
    procedure:

      $ ./configure
      $ make
      $ cd lisp
      $ make recompile EMACS=../src/emacs
      $ cd ..
      $ make

    (If you want to install the Emacs binary, type "make install" instead
    of "make" in the last command.)

If this is not the best strategy, INSTALL.CVS should be changed.

(Note however that for people with fast machines, running `make
maintainer-clean' and `make bootstrap' is so fast that it is not even
worth the trouble trying anything else.)

In case of trouble we recommend first to update loaddefs.el and if
this does not solve the problem, to run `make bootstrap'.  That used
to be sufficient.  After a relatively recent change it no longer is.
One has to first do `make maintainer-clean', then `make bootstrap'.
This is not pointed out in INSTALL.CVS.

There are two solutions.  The first is to point it out in INSTALL.CVS.
One problem with that is that people already familiar with
INSTALL.CVS, do not reread it every few days.

A more radical solution is to revert the recent change to `make
bootstrap'.  That change made `make bootstrap' run faster, but at a
cost.  We get reports on trouble during bootstrapping that are only
due to failure to run `make maintainer-clean' on a regular basis.
Failing to run `make maintainer-clean' does not necessarily cause
bootstrapping to fail.  Instead, it can cause bugs in the bootstrapped
Emacs.  So every time somebody reports a bug that seems
irreproducible, there is always the possibility that it was due
failure to run `make maintainer-clean'.

Has anybody benefited sufficiently from the change in `make bootstrap'
to compensate for all the time that many people are losing as a result
of it?  I am inclined to believe that the change to `make bootstrap'
should be reverted.

Sincerely,

Luc.

  reply	other threads:[~2004-07-01  3:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 20:55 appears CVS build is broken (tty-supports-face-attributes-p)? John Owens
2004-06-30  1:28 ` Luc Teirlinck
2004-06-30  2:09 ` Miles Bader
2004-06-30  5:32 ` Stefan Reichör
2004-06-30 17:01   ` John Owens
2004-07-01  2:17     ` Miles Bader
2004-07-01  3:38       ` Luc Teirlinck [this message]
2004-07-01  3:52         ` Miles Bader
2004-07-01 10:43         ` Stefan
2004-07-01  3:47       ` Luc Teirlinck

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=200407010338.i613cxZ25774@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=john_owens@yahoo.com \
    --cc=xsteve@riic.at \
    /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.