Mercurial > emacs
view BUGS @ 49259:d6211ef9bbb4
(loaddefs.el): Invoke make to build stub file
using appropriate rule for build environment.
(loaddefs.el-SH, loaddefs.el-CMD): New targets. Include small set
of autoloads and defvars, sufficient to dump bootstrap emacs.
(update-subdirs-SH): Use hard-coded list of top-level lisp
subdirs, because find program on Windows is not compatible with
Unix find.
(compile-CMD, compile-SH): Use `batch-byte-compile-if-not-done'.
Explicitly load loaddefs.el so that bootstrap emacs can compile
properly.
(bootstrap-clean): Add dependency on loaddefs.el, to ensure
minimal stub sufficient for dumping bootstrap emacs is available.
author | Andrew Innes <andrewi@gnu.org> |
---|---|
date | Wed, 15 Jan 2003 12:14:05 +0000 |
parents | af68d12218d0 |
children | 8ce686bd7f4f |
line wrap: on
line source
If you think you may have found a bug in GNU Emacs, please read the Bugs section of the Emacs manual for advice on (1) how to tell when to report a bug, and (2) how to write a useful bug report and what information it needs to have. There are three ways to read the Bugs section. (1) In a printed copy of the Emacs manual. You can order one from the Free Software Foundation; see the file etc/ORDERS. But if you don't have a copy on hand and you think you have found a bug, you shouldn't wait to get a printed manual; you should read the section right away as described below. (2) With Info. Start Emacs, do C-h i to enter Info, then m Emacs RET to get to the Emacs manual, then m Bugs RET to get to the section on bugs. Or use standalone Info in a like manner. (Standalone Info is part of the Texinfo distribution, not part of the Emacs distribution.) (3) By hand. Do cat info/emacs* | more "+/^File: emacs, Node: Bugs," Please first check the file etc/PROBLEMS (e.g. with C-h P in Emacs) to make sure it isn't a known issue.