mirror of
git://git.sv.gnu.org/emacs.git
synced 2026-02-23 08:20:41 -08:00
6553950651
* src/s/usg5-4-common.h (HAVE_TERMIOS): * src/s/template.h (HAVE_TERMIOS): * src/s/gnu-linux.h (HAVE_TERMIOS): * src/s/darwin.h (HAVE_TERMIOS): * src/s/cygwin.h (HAVE_TERMIOS): * src/s/bsd-common.h (HAVE_TERMIOS): * src/s/aix4-2.h (HAVE_TERMIOS): * src/s/hpux10-20.h (HAVE_TERMIOS): Do not define, it is assumed defined on all non-MS platforms. (HAVE_PSTAT_GETDYNAMIC): Do not define, autoconf does it.
125 lines
5 KiB
C
125 lines
5 KiB
C
/* Template for system description header files.
|
|
This file describes the parameters that system description files
|
|
should define or not.
|
|
|
|
Copyright (C) 1985, 1986, 1992, 1999, 2001, 2002, 2003, 2004, 2005,
|
|
2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc.
|
|
|
|
This file is part of GNU Emacs.
|
|
|
|
GNU Emacs is free software: you can redistribute it and/or modify
|
|
it under the terms of the GNU General Public License as published by
|
|
the Free Software Foundation, either version 3 of the License, or
|
|
(at your option) any later version.
|
|
|
|
GNU Emacs is distributed in the hope that it will be useful,
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
GNU General Public License for more details.
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>. */
|
|
|
|
|
|
/* Define symbols to identify the version of Unix this is.
|
|
Define all the symbols that apply correctly. */
|
|
|
|
/* #define USG5 */
|
|
/* #define USG */
|
|
/* #define HPUX */
|
|
/* #define BSD4_2 */
|
|
/* #define BSD4_3 */
|
|
/* #define BSD_SYSTEM */
|
|
|
|
/* SYSTEM_TYPE should indicate the kind of system you are using.
|
|
It sets the Lisp variable system-type. */
|
|
|
|
#define SYSTEM_TYPE "berkeley-unix"
|
|
|
|
/* Emacs can read input using SIGIO and buffering characters itself,
|
|
or using CBREAK mode and making C-g cause SIGINT.
|
|
The choice is controlled by the variable interrupt_input.
|
|
|
|
Define INTERRUPT_INPUT to make interrupt_input = 1 the default (use SIGIO)
|
|
|
|
Emacs uses the presence or absence of the SIGIO and BROKEN_SIGIO macros
|
|
to indicate whether or not signal-driven I/O is possible. It uses
|
|
INTERRUPT_INPUT to decide whether to use it by default.
|
|
|
|
SIGIO can be used only on systems that implement it (4.2 and 4.3).
|
|
CBREAK mode has two disadvantages
|
|
1) At least in 4.2, it is impossible to handle the Meta key properly.
|
|
I hear that in system V this problem does not exist.
|
|
2) Control-G causes output to be discarded.
|
|
I do not know whether this can be fixed in system V.
|
|
|
|
Another method of doing input is planned but not implemented.
|
|
It would have Emacs fork off a separate process
|
|
to read the input and send it to the true Emacs process
|
|
through a pipe. */
|
|
#define INTERRUPT_INPUT
|
|
|
|
/* Letter to use in finding device name of first pty,
|
|
if system supports pty's. 'a' means it is /dev/ptya0. */
|
|
#define FIRST_PTY_LETTER 'a'
|
|
|
|
/* Define HAVE_PTYS if the system supports pty devices. */
|
|
#define HAVE_PTYS
|
|
|
|
/* subprocesses should be undefined if you do NOT want to
|
|
have code for asynchronous subprocesses
|
|
(as used in M-x compile and M-x shell).
|
|
Currently only MSDOS does not support this. */
|
|
|
|
/* #undef subprocesses */
|
|
|
|
/* Define CLASH_DETECTION if you want lock files to be written
|
|
so that Emacs can tell instantly when you try to modify
|
|
a file that someone else has modified in his Emacs. */
|
|
#define CLASH_DETECTION
|
|
|
|
/* Define this if your operating system declares signal handlers to
|
|
have a type other than the usual. `The usual' is `void' for ANSI C
|
|
systems (i.e. when the __STDC__ macro is defined), and `int' for
|
|
pre-ANSI systems. If you're using GCC on an older system, __STDC__
|
|
will be defined, but the system's include files will still say that
|
|
signal returns int or whatever; in situations like that, define
|
|
this to be what the system's include files want. */
|
|
/* #define SIGTYPE int */
|
|
|
|
/* If the character used to separate elements of the executable path
|
|
is not ':', #define this to be the appropriate character constant. */
|
|
/* #define SEPCHAR ':' */
|
|
|
|
/* ============================================================ */
|
|
|
|
/* Here, add any special hacks needed to make Emacs work on this
|
|
system. For example, you might define certain system call names
|
|
that don't exist on your system, or that do different things on
|
|
your system and must be used only through an encapsulation (which
|
|
you should place, by convention, in sysdep.c). */
|
|
|
|
/* If the system's imake configuration file defines `NeedWidePrototypes'
|
|
as `NO', we must define NARROWPROTO manually. Such a define is
|
|
generated in the Makefile generated by `xmkmf'. If we don't
|
|
define NARROWPROTO, we will see the wrong function prototypes
|
|
for X functions taking float or double parameters. */
|
|
|
|
/* #define NARROWPROTO 1 */
|
|
|
|
/* ============================================================ */
|
|
|
|
/* After adding support for a new system, modify the large case
|
|
statement in configure.in to recognize reasonable
|
|
configuration names, and add a description of the system to
|
|
`etc/MACHINES'.
|
|
|
|
Check for any tests of $opsys in configure.in, and add an entry
|
|
for the new system if needed.
|
|
|
|
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: 4b426b11-cb2e-4c0e-a488-e663f76a0515
|
|
(do not change this comment) */
|