Mercurial > emacs
changeset 42821:449c8f0630dd
Wording changes suggested by Richard Stallman.
| author | Eli Zaretskii <eliz@gnu.org> |
|---|---|
| date | Fri, 18 Jan 2002 07:53:34 +0000 |
| parents | 6477316b4dd9 |
| children | b2bfe0b4018b |
| files | etc/PROBLEMS |
| diffstat | 1 files changed, 8 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/etc/PROBLEMS Fri Jan 18 05:45:17 2002 +0000 +++ b/etc/PROBLEMS Fri Jan 18 07:53:34 2002 +0000 @@ -27,7 +27,8 @@ Note that this problem does not pertain to the MS-Windows port of Emacs, since it doesn't use the preprocessor to generate Makefiles. -* Building Emacs with a system compiler fails during link stage. +* Building Emacs with a system compiler fails to link because of an +undefined symbol such as __eprintf which does not appear in Emacs. This can happen if some of the libraries linked into Emacs were built with GCC, but Emacs itself is being linked with a compiler other than @@ -40,6 +41,9 @@ make CC=gcc +Since the .o object files already exist, this will not recompile Emacs +with GCC, but just restart by trying again to link temacs. + * Building the MS-Windows port with Cygwin GCC can fail. Emacs may not build using recent Cygwin builds of GCC, such as Cygwin @@ -808,9 +812,9 @@ cleanly before exiting Emacs. For more details, see the FAQ at http://www.gnu.org/software/emacs/windows/. -* Windows 95/98/ME crashes when trying to run non-existent subprocesses. - -When a subprocess you are trying to run is not found on the PATH, +* Windows 95/98/ME crashes when Emacs invokes non-existent programs. + +When a program you are trying to run is not found on the PATH, Windows might respond by crashing or locking up your system. In particular, this has been reported when trying to compile a Java program in JDE when javac.exe is installed, but not on the system