Mercurial > emacs
view BUGS @ 56512:d341e83af4f2
Removed the various "echo." lines from lisp\makefile.w32-in and nt\makefile.w32-in.
They caused mingw32-make.exe bootstrap to fail with the following error if cmd.exe
was being used as the shell:
"process_begin: CreateProcess((null), echo., ...) failed."
I replaced the "@echo." lines in nt\makefile.w32-in with "@echo ." This writes a .
to the screen but that is far more desirable than make bootstrap failing.
I replaced the "echo. ..." line in lisp\makefile.w32-in with "echo ;;; ...". This
writes an extra comment line to loaddefs.el. Again this is far more desirable than
make bootstrap failing.
NOTE: I am using cmd.exe as my shell when building Emacs with MinGW instead of
the sh.exe that comes with msys because when I use sh.exe as my shell, loaddefs.el
does not get properly generated and I get various auto load errors.
author | Ben Key <bkey1@tampabay.rr.com> |
---|---|
date | Sat, 24 Jul 2004 04:52:27 +0000 |
parents | 8ce686bd7f4f |
children | fb8bf24d2eb9 |
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 C-e in Emacs) to make sure it isn't a known issue.