From: "D. Goel" <deego@glue.umd.edu>
Cc: eliz@is.elta.co.il, emacs-devel@gnu.org
Subject: Re: NT Emacs make problem..
Date: 11 Jun 2002 13:11:23 -0400 [thread overview]
Message-ID: <ap3lm9lhhac.fsf@student1.physics.umd.edu> (raw)
In-Reply-To: <200206101014.g5AAEOd01405@aztec.santafe.edu>
> Sure, i shall write down all the 'directions' that emerge from this
> thread into that INSTALL-CVS i posted, and finally post the completed
> INSTALL-CVS to the list..
>
> Please do. However, if it is as simple as it seems to be, we need not
> fuss with a license notice. They are not needed on very small files.
'COPYING NOTICE' removed.
>
> We may not need any more directions
Cool, we are done with this file then :). I am including the file at
the end of this mail. perhaps, Could the maintainers please install it?
Have a good day,
DG <http://www.glue.umd.edu/~deego/>
--
====================================================
Building and Installing Emacs
from the CVS
Copyright (c) 2001 Free Software Foundation, Inc.
The build-instructions for a release and CVS are slightly different.
The tarball in an Emacs release usually contains byte-compiled code
for some of the files. However, for the files checked out from CVS,
there are no byte-compiled files.
To build emacs from a CVS checkout, follow the instructions as you
would for the tarball, except that replace the initial 'make' by 'make
bootstrap', e.g.:
$ ./configure
$ make bootstrap
next prev parent reply other threads:[~2002-06-11 17:11 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
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 [this message]
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=ap3lm9lhhac.fsf@student1.physics.umd.edu \
--to=deego@glue.umd.edu \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.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).