From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: eliz@is.elta.co.il, deego@glue.umd.edu, emacs-devel@gnu.org
Subject: Re: NT Emacs make problem..
Date: Sat, 08 Jun 2002 13:20:33 -0700 [thread overview]
Message-ID: <E17GmhN-0005cw-00@giblet> (raw)
In-Reply-To: <200206081915.g58JFrE28855@aztec.santafe.edu> (message from0Richard Stallman on Sat, 8 Jun 2002 13:15:53 -0600 (MDT))
From: Richard Stallman <rms@gnu.org>
Date: Sat, 8 Jun 2002 13:15:53 -0600 (MDT)
Do you mean that doing the checkout with CVSREAD=1 leads to bad source
files?
sorry i wasn't more precise: CVSREAD=1 causes "cvs checkout" to create
read-only files. some steps in "make bootstrap" fail because they need
to recreate or update files, and cannot do so. (source files are not
corrupted, in any case.)
there was discussion previously about some script to be run immediately
after a "cvs checkout" but before "make bootstrap". i suggest we write
that script, include "chmod +w $cannot_be_ro_file_list", and publish the
way to build emacs from cvs as:
cvs checkout ...
cd emacs
sh -x prep-bootstrap # ("-x" for entertainment purposes :-)
make bootstrap
prep-bootstrap need not be distributed.
thi
next prev parent reply other threads:[~2002-06-08 20:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SUN.3.91.1020605143252.7779A-100000@is>
[not found] ` <ap3bsapg081.fsf@student1.physics.umd.edu>
[not found] ` <9735-Wed05Jun2002210858+0300-eliz@is.elta.co.il>
2002-06-07 0:44 ` NT Emacs make problem Richard Stallman
2002-06-07 1:11 ` Thien-Thi Nguyen
2002-06-08 19:15 ` Richard Stallman
2002-06-08 20:20 ` Thien-Thi Nguyen [this message]
2002-06-10 10:15 ` Richard Stallman
2002-06-10 10:39 ` Thien-Thi Nguyen
2002-06-11 17:16 ` D. Goel
2002-06-07 13:37 ` Eli Zaretskii
2002-06-07 14:09 ` D. Goel
2002-06-07 15:07 ` Simon Josefsson
2002-06-07 16:47 ` D. Goel
2002-06-08 19:15 ` Richard Stallman
2002-06-09 3:11 ` D. Goel
2002-06-10 10:14 ` Richard Stallman
2002-06-10 11:34 ` Kai Großjohann
2002-06-11 17:11 ` D. Goel
2002-06-11 19:29 ` Kai Großjohann
2002-06-12 12:14 ` Richard Stallman
2002-06-12 13:13 ` Stefan Monnier
2002-06-13 4:55 ` Eli Zaretskii
2002-06-13 21:46 ` Richard Stallman
2002-06-12 13:37 ` Kai Großjohann
2002-06-13 21:47 ` Richard Stallman
2002-06-12 14:33 ` Andreas Schwab
2002-06-13 14:36 ` D. Goel
2002-06-12 2:34 ` Richard Stallman
2002-06-12 4:48 ` Eli Zaretskii
2002-06-12 12:42 ` Richard Stallman
2002-06-12 8:28 ` Simon Josefsson
2002-06-09 15:48 ` Kai Großjohann
2002-06-09 22:44 ` Kim F. Storm
2002-06-10 23:44 ` Richard Stallman
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=E17GmhN-0005cw-00@giblet \
--to=ttn@giblet.glug.org \
--cc=deego@glue.umd.edu \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=ttn@glug.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).