diff src/m/ibms390.h @ 96833:c06568fd3844

* s/usg5-4.h (LIBS_SYSTEM): Remove, system for which this was added not supported anymore. * s/usg5-4-2.h (LIBS_SYSTEM): * s/sol2.h (LIBS_SYSTEM): Do not undefine. * s/netbsd.h (GETPGRP_NO_ARG, N_TRELOFF): * s/lynxos.h (GETPGRP_NO_ARG): * s/hpux10-20.h (NO_SIOCTL_H): * s/gnu.h (GETPGRP_NO_ARG): * s/gnu-linux.h (NO_SIOCTL_H): * s/freebsd.h (GETPGRP_NO_ARG, N_TRELOFF): * s/cygwin.h (GETPGRP_NO_ARG): * s/irix6-5.h (LIBS_SYSTEM, GETPGRP_NO_ARG): Remove, unused. (C_DEBUG_SWITCH): Remove duplicate definition. * m/ibms390.h: Remove boilerplate comments. * sysdep.c (closedir): Use SOLARIS2 instead of sun && USG5_4. * process.c (HAVE_SERIAL): Consolidate ifdefs. (wait_reading_process_output): Remove code for SunOS, platform not supported anymore. Use SOLARIS2 instead of sun.

--- a/src/m/ibms390.h	Sun Jul 20 00:53:41 2008 +0000
+++ b/src/m/ibms390.h	Sun Jul 20 13:03:56 2008 +0000
@@ -57,36 +57,5 @@
 
 #define VIRT_ADDR_VARIES
 
-/* Define NO_REMAP if memory segmentation makes it not work well
-   to change the boundary between the text section and data section
-   when Emacs is dumped.  If you define this, the preloaded Lisp
-   code will not be sharable; but that's better than failing completely.  */
-
-/*#define NO_REMAP */
-
-/* Some really obscure 4.2-based systems (like Sequent DYNIX)
- * do not support asynchronous I/O (using SIGIO) on sockets,
- * even though it works fine on tty's.  If you have one of
- * these systems, define the following, and then use it in
- * config.h (or elsewhere) to decide when (not) to use SIGIO.
- *
- * You'd think this would go in an operating-system description file,
- * but since it only occurs on some, but not all, BSD systems, the
- * reasonable place to select for it is in the machine description
- * file.
- */
-
-/*#define NO_SOCK_SIGIO*/
-
-
-/* After adding support for a new system, modify the large case
-   statement in the `configure' script to recognize reasonable
-   configuration names, and add a description of the system to
-   `etc/MACHINES'.
-
-   If you've just fixed a problem in an existing configuration file,
-   you should also check `etc/MACHINES' to make sure its descriptions
-   of known problems in that configuration should be updated.  */
-
 /* arch-tag: d8a0ffa4-a8f0-4736-90d3-7fd7b21b8314
    (do not change this comment) */