mirror of
https://git.savannah.gnu.org/git/emacs.git
synced 2024-11-24 07:20:37 +00:00
d5ef6196df
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. |
||
|---|---|---|
| .. | ||
| icons | ||
| inc | ||
| .gitignore | ||
| addpm.c | ||
| addsection.c | ||
| ChangeLog | ||
| cmdproxy.c | ||
| config.nt | ||
| configure.bat | ||
| COPYING | ||
| ddeclient.c | ||
| emacs.rc | ||
| envadd.bat | ||
| ftime-nostartup.bat | ||
| ftime.bat | ||
| gmake.defs | ||
| INSTALL | ||
| makefile.w32-in | ||
| multi-install-info.bat | ||
| nmake.defs | ||
| paths.h | ||
| preprep.c | ||
| README | ||
| runemacs.c | ||
| subdirs.el | ||
Emacs for Windows NT/2000 and Windows 95/98/ME Copyright (c) 2001 Free Software Foundation, Inc. See the end of the INSTALL file in this directory for copying permissions. This directory contains support for compiling and running GNU Emacs on Windows NT, Windows 95, and their successors. This port supports all of the major functionality of the Unix version, including subprocesses, windowing features (fonts, colors, scroll bars, multiple frames, etc.), and networking support. Precompiled distributions are also available; ftp to ftp://ftp.gnu.org/gnu/windows/emacs/latest/ for the latest precompiled distributions. * Building and installing See the INSTALL file in this directory for detailed instructions on building and installing Emacs on your system. * Further information There is a web page that serves as a FAQ for the Windows port of Emacs (a.k.a. NTEmacs) at: http://www.gnu.org/software/emacs/windows/ntemacs.html There is also a mailing list for discussing issues related to this port of Emacs. For information about the list, see this Web page: http://mail.gnu.org/mailman/listinfo/help-emacs-windows To ask questions on the mailing list, send email to help-emacs-windows@gnu.org. (You don't need to subscribe for that.) To subscribe to the list or unsubscribe from it, fill the form you find at http://mail.gnu.org/mailman/listinfo/help-emacs-windows as explained there. Another valuable source of information and help which should not be overlooked is the various Usenet news groups dedicated to Emacs. These are particularly good for help with general issues which aren't specific to the Windows port of Emacs. The main news groups to use for seeking help are: gnu.emacs.help comp.emacs There are also fairly regular postings and announcements of new or updated Emacs packages on this group: gnu.emacs.sources * Reporting bugs If you encounter a bug in this port of Emacs, we would like to hear about it. First check the file etc/PROBLEMS and the FAQ on the web page above to see if the bug is already known and if there are any workarounds. If not, then check whether the bug has something to do with code in your .emacs file, e.g. by invoking Emacs with the "-q --no-site-file" options. If you decide that it is a bug in Emacs that might be specific to the Windows port, send a message to the help-emacs-windows@gnu.org mailing list describing the bug, the version of Emacs that you are using, and the operating system that you are running on (Windows NT, 95 or 98 including service pack level if known). If the bug is related to subprocesses, also specify which shell you are using (e.g., include the values of `shell-file-name' and `shell-explicit-file-name' in your message). If you think the bug is not specific to the Windows port of Emacs, then it is better to mail the bug report to bug-gnu-emacs@gnu.org so that it will be seen by the right people. If Emacs has been set up to send mail, you can use the command M-x report-emacs-bug to create and send the bug report, but in some cases there is a function to report bugs in a specific package; e.g. M-x gnus-bug for Gnus, M-x c-submit-bug-report for C/C++/Java mode, etc.