From e23dc1e2f07b476bc27d77037331b00a517eb5e3 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Wed, 2 Jun 2010 22:50:48 -0700 Subject: Remove NO_SOCK_SIGIO references. * src/m/template.h (NO_SOCK_SIGIO): Remove, no longer used. * nextstep/DEV-NOTES: Remove out-of-date information. --- src/ChangeLog | 2 ++ src/m/template.h | 11 ----------- 2 files changed, 2 insertions(+), 11 deletions(-) (limited to 'src') diff --git a/src/ChangeLog b/src/ChangeLog index 3f66710b2bb..864d873e30e 100644 --- a/src/ChangeLog +++ b/src/ChangeLog @@ -1,5 +1,7 @@ 2010-06-03 Glenn Morris + * m/template.h (NO_SOCK_SIGIO): Remove, no longer used. + * m/hp800.h (alloca) [__NetBSD__ && __GNUC__]: No need to define it, now that AH_BOTTOM does it. diff --git a/src/m/template.h b/src/m/template.h index 2807cd913ec..3beac1a7808 100644 --- a/src/m/template.h +++ b/src/m/template.h @@ -58,17 +58,6 @@ along with GNU Emacs. If not, see . */ 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 machine, modify the large case statement in configure.in to recognize reasonable configuration names, and add a description of the system to -- cgit v1.2.1