From: Stefan <monnier@iro.umontreal.ca>
Cc: john_owens@yahoo.com, xsteve@riic.at, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: appears CVS build is broken (tty-supports-face-attributes-p)?
Date: 01 Jul 2004 06:43:13 -0400 [thread overview]
Message-ID: <m1acyk6mni.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <200407010338.i613cxZ25774@raven.dms.auburn.edu>
> In practice, people are going to do what we _ask_ them to do in
> INSTALL.CVS:
Somehow I doubt it, seeing how they can't even follow the two-lines that
say "don't post to gnu.emacs.help".
> Normally, it is not necessary to use "make bootstrap" after every CVS
> update. Unless there are problems, we suggest the following
> procedure:
> $ ./configure
Shouldn't be necessary.
> $ make
> $ cd lisp
> $ make recompile EMACS=../src/emacs
> $ cd ..
> $ make
Of course, we should strive to turn the above into just `make'.
> (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.)
You must have really impressingly fast machines around then, because my
1 year old Opteron is very much too slow for
"make maintainer-clean bootstrap".
> 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.
I think I have to agree. :-(
Stefan
next prev parent reply other threads:[~2004-07-01 10:43 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
2004-07-01 10:43 ` Stefan [this message]
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=m1acyk6mni.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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.