Do not preprocess src/Makefile.in.

* configure.in: Do not preprocess src/Makefile.in.
(cpp_undefs, CPP_NEED_TRADITIONAL): Remove.
(AC_EGREP_CPP): Test no longer needed.
* configure: Regenerate.

* config.bat: Do not preprocess src/Makefile.in.

* make-dist: No more Makefile.c files.

* INSTALL, src/README: Makefiles are not preprocessed.

* src/Makefile.in, src/autodeps.mk, src/deps.mk, src/ns.mk:
Convert comments to Makefile format.

* lib-src/Makefile.in (distclean): No more Makefile.c.
* src/Makefile.in (bootstrap-clean): No more Makefile.c.

* admin/notes/cpp: Remove file.

* admin/quick-install-emacs (AVOID): No more Makefile.c files.

* etc/PROBLEMS, etc/MACHINES: Remove details of cpp problems which can
no longer occur.

2 files changed, 1 insertions, 49 deletions

diff --git a/etc/MACHINES b/etc/MACHINES
index 8fc79ab0d1d..aa5d766e8dd 100644
--- a/etc/MACHINES
+++ b/etc/MACHINES
@@ -198,8 +198,7 @@ IBM RS/6000 (rs6000-ibm-aix*)
 
 IBM System/390 running GNU/Linux (s390-*-linux-gnu)
 
-  As of Emacs 21.2, a 31-bit only version is supported on this
-  system.
+  As of Emacs 21.2, a 31-bit only version is supported on this system.
 
 Intel 386 (i386-*-freebsd,      i386-*-linux-gnu,
            i386-*-sol2.4,       i386-intsys-sysv,
@@ -247,11 +246,6 @@ Intel 386 (i386-*-freebsd,      i386-*-linux-gnu,
   do `gmake install MAKE=gmake'.  However, more recently it is
   reported that using the system Make on NetBSD 1.3.1 works ok.
 
-  If you are using System V release 4.2, you may find that `cc -E'
-  puts spurious spaces in `src/xmakefile'.  If that happens,
-  specify CPP=/lib/cpp as an option when you run make.
-  There is no problem if you compile with GCC.
-
   Note that use of Linux with GCC 2.4 and the DLL 4.4 libraries
   requires the experimental "net 2" network patches (no relation to
   Berkeley Net 2).  There is a report that (some version of) Linux
@@ -491,10 +485,6 @@ System V rel 4.0.3 and 4.0.4 (usg5.4)
   If you get compilation errors about wrong number of
   arguments to getpgrp, define GETPGRP_NO_ARG.
 
-  The standard C preprocessor may generate xmakefile incorrectly.  However,
-  /lib/cpp will work, so use `make CPP=/lib/cpp'.  Standard cpp
-  seems to work OK under Dell 2.2.
-
   Some versions 3 and earlier of V.4, on the Intel 386 and 860, had
   problems in the X11 libraries.  These prevent Emacs from working
   with X.  You can use Emacs with X provided your copy of X is based
diff --git a/etc/PROBLEMS b/etc/PROBLEMS
index b3cda374c51..65e3920eee3 100644
--- a/etc/PROBLEMS
+++ b/etc/PROBLEMS
@@ -2373,18 +2373,6 @@ The solution is to tell configure to use the correct C preprocessor
 for your C compiler (CPP="/opt/SUNWspro/bin/cc -E" in the above
 example).
 
-*** `configure' fails with ``"junk.c", line 660: invalid input token: 8.elc''
-
-The final stage of the Emacs configure process uses the C preprocessor
-to generate the Makefiles.  Errors of this form can occur if the C
-preprocessor inserts extra whitespace into its output.  The solution
-is to find the switches that stop your preprocessor from inserting extra
-whitespace, add them to CPPFLAGS, and re-run configure.  For example,
-this error can occur on Solaris 10 when using the Sun Studio compiler
-``Sun C 5.8'' with its preprocessor CPP="/opt/SUNWspro/bin/cc -E".
-The relevant switch in this case is "-Xs" (``compile assuming
-(pre-ANSI) K & R C style code'').
-
 ** Compilation
 
 *** Building Emacs over NFS fails with ``Text file busy''.
@@ -2427,32 +2415,6 @@ you are working on the host called `marvin'.  Then an entry in the
 
 The solution is to remove this line from `etc/fstab'.
 
-*** Building Emacs with GCC 2.9x fails in the `src' directory.
-
-This may happen if you use a development version of GNU `cpp' from one
-of the GCC snapshots between Oct 2000 and Feb 2001, or from a released
-version of GCC newer than 2.95.2 which was prepared around those
-dates; similar problems were reported with some snapshots of GCC 3.1
-around Sep 30 2001.  The preprocessor in those versions is
-incompatible with a traditional Unix cpp (e.g., it expands ".." into
-". .", which breaks relative file names that reference the parent
-directory; or inserts TAB characters before lines that set Make
-variables).
-
-The solution is to make sure the preprocessor is run with the
-`-traditional' option.  The `configure' script does that automatically
-when it detects the known problems in your cpp, but you might hit some
-unknown ones.  To force the `configure' script to use `-traditional',
-run the script like this:
-
-  CPP='gcc -E -traditional' ./configure ...
-
-(replace the ellipsis "..." with any additional arguments you pass to
-the script).
-
-Note that this problem does not pertain to the MS-Windows port of
-Emacs, since it doesn't use the preprocessor to generate Makefiles.
-
 *** src/Makefile and lib-src/Makefile are truncated--most of the file missing.
 *** Compiling wakeup, in lib-src, says it can't make wakeup.c.