all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
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: Thu, 01 Jul 2004 12:52:26 +0900	[thread overview]
Message-ID: <buok6xov0xx.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <200407010338.i613cxZ25774@raven.dms.auburn.edu> (Luc Teirlinck's message of "Wed, 30 Jun 2004 22:38:59 -0500 (CDT)")

Luc Teirlinck <teirllm@dms.auburn.edu> writes:
>    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:

My above message assumed that people (1) have emacs already installed,
and (2) are using GNU make.  It seems slightly dubious for INSTALL.CVS
to assume those things, but in practice they're probably often true.

Note that I also recommend recompiling the lisp files _before_ compiling
emacs, as sometimes lisp changes can affect the emacs build, but again
that requires a pre-existing emacs binary.

I don't understand why INSTALL.CVS says to re-run ./configure though --
that seems almost never necessary (as the Makefile will do so
automatically).

-Miles
-- 
My spirit felt washed.  With blood.  [Eli Shin, on "The Passion of the Christ"]

  reply	other threads:[~2004-07-01  3:52 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
2004-07-01  3:52         ` Miles Bader [this message]
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=buok6xov0xx.fsf@mctpc71.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=emacs-devel@gnu.org \
    --cc=john_owens@yahoo.com \
    --cc=miles@gnu.org \
    --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.