Commit f4b79972 authored by Eli Zaretskii's avatar Eli Zaretskii

Update the entry for the HITACHI SR2001/SR2201 series.

parent 44abba96
This is a list of the status of GNU Emacs on various machines and systems.
For each system and machine, we give the configuration name you should
pass to the `configure' script to prepare to build Emacs for that
system/machine.
The `configure' script uses the configuration name to decide which
machine and operating system description files `src/config.h' should
include. The machine description files are all in `src/m', and have
names similar to, but not identical to, the machine names used in
configuration names. The operating system files are all in `src/s',
and are named similarly. See the `configure' script if you need to
know which configuration names use which machine and operating system
description files.
If you add support for a new configuration, add a section to this
file, and then edit the `configure' script to tell it which
configuration name(s) should select your new machine description and
system description files.
Here are the configurations Emacs is intended to work with, with the
corresponding configuration names. You can postpend version numbers
to operating system names (i.e. sunos4.1) or architecture names (i.e.
hppa1.1). If you leave out the version number, the `configure' script
will configure Emacs for the latest version it knows about.
Acorn RISCiX (arm-acorn-riscix1.2)
Emacs 19.29 has changes that ought to support RISCiX 1.2.
Due to a bug in the RISCiX C compiler (3.4.5), emacs must
be built with gcc (versions 2.5.8 onwards).
In addition, you will need GNU sed and GNU make, as the RISCiX release
versions of these utilities cannot cope with building emacs-19!
GNU sed should be configured with:
env 'DEFS=-Dgetopt=gnu_getopt -Dopterr=gnu_opterr -Doptind=gnu_optind \
-Doptarg=gnu_optarg' ./configure
GNU make (3.72+) should be configured with:
env 'CFLAGS=-Dgetopt=gnu_getopt -Dopterr=gnu_opterr -Doptind=gnu_optind \
-Doptarg=gnu_optarg' ./configure
Emacs may be configured to use the X toolkit, by adding --with-x-toolkit
to the configure command. If you do this, you will need to edit the line
in src/Makefile which defines LIBW (about line 59) to read:
LIBW= -lXaw_n
This ensures that the non-shared widget library is used.
It is unlikely that this version of emacs will work with RISCiX 1.1.
Alliant (fx80-alliant-bsd):
18.52 worked on system version 4. Previous Emacs versions were
known to work on previous system versions.
If you are using older versions of their operating system, you may
need to edit `src/config.h' to use `m/alliant1.h' (on version 1) or
`m/alliant.h' (on versions 2 and 3).
Alliant FX/2800 (i860-alliant-bsd)
Known to work with 19.26 and OS version 2.2, compiler version 1.3.
Alpha (DEC) running OSF/1 or GNU/Linux (alpha-dec-osf1, alpha-dec-linux-gnu)
For OSF/1 (aka Digital Unix) version 4.0, update 386,
it is reported that you need to run configure this way:
configure --x-includes=/usr/include --x-libraries=/usr/shlib
For 4.0 revision 564, and 4.0A and 4.0B, Emacs 20 seems to work
with no special configuration options. However, if you use GCC as
your compiler, you will need version 2.8.1 or later, as older
versions fail to build with a message "Invalid dimension for the
charset-ID 160".
Note that the X11 libraries on GNU/Linux systems for the Alpha are
said to have bugs that prevent Emacs from working with X (as of
November 1995). Recent releases work (July 2000).
Altos 3068 (m68k-altos-sysv)
18.52 was said to work, provided you don't compile unexec.c with -O.
Amdahl UTS (580-amdahl-sysv)
Small changes for 18.38 were merged in 18.39. It is mostly
working, but at last report a bug sometimes causes Emacs to
grab very large amounts of memory. No fix or explanation
has yet been reported. It may be possible to find this bug
if you find which Emacs command it happens within and then
run that command with a breakpoint set at malloc.
The 5.2u370 compiler is so brain damaged that it is not
even worth trying to use it. Success was obtained with the
uts native C compiler on uts version 5.2.5.
Apollo running X Windows (m68k-apollo-bsd)
Apollo version now supports dumping. It has been tested on SR10.3 and
SR10.4. It certainly requires at least SR10.0, and maybe SR10.2. Be sure
to build in the BSD environment.
By default, everything is compiled with the switch "-W0,-opt,2". Don't try
to change this to full optimization (-O). The full optimizer (in Domain CC
6.7, 6.8 and 6.9) generates some bad code in several modules which causes
the emacs window, under X, to be refreshed with each keystroke.
The configuration stuff should work for the most part. However, some Domain
installations may have to edit src/Makefile manually after it is created.
There are too many versions of both cc and X to automate this easily.
In `lib-src/Makefile', emacsclient and emacsserver compile and work fine
under CC 6.9. They now probably work under other versions of the compiler,
as well.
The Apollo Domain CC compiler will issue quite a few warning messages,
mostly complaining about incompatible pointers. In general, these are
harmless and can be ignored. If you discover otherwise, please submit a bug
report identifying the problem in detail.
When you try to dump emacs, you may get the message ".rwdi section needs
relocation." This means you are linking with some code that has compressed
data sections. In some cases this comes from linking with X libraries. Try
using shared X libraries instead. With some versions of Domain/OS this is
as simple as removing the "-lX11" from the LIBX line in src/Makefile.
When running the configure script, use the configuration name
"m68k-apollo-bsd". You will also need to use the "-with-gcc=no" and
"-with-x" options. Depending upon your site configuration, you may have to
use other configure options, as well. Examine the INSTALL file for other
configure options.
Check out the file 'lisp/x-apollo.el'. To use it, add
(load "x-apollo")
to your .emacs file. It provides useful default Apollo function key
bindings.
AT&T 3b2, 3b5, 3b15, 3b20 (we32k-att-sysv)
Emacs will probably not work with certain kernel constants too small.
In param.h CDLIMIT should be at least (1L << 12) in order to allow
processes to write up to 2 Mbyte files. This parameter is configurable
by normal means in /etc/master.d/kernel; examine that file for the
symbol CDLIMIT or ULIMIT, and raise it by several powers of 2. Then
do normal kernel rebuild things via "cd /boot; mkboot -k KERNEL" and so
forth.
In seg.h NSEGP and STACKSEG should be at least 16 and 4 respectively
to allow processes with total size of up to 2Mbytes.
However, I'm told it is unlikely this would fail to be true.
The MAXMEM may also prevent Emacs from running. The file
3B-MAXMEM in this directory explains how to increase MAXMEM.
On some of these machines, you may need to define IN_SCCS_ID
in config.h to make Emacs work. Supposedly you can tell whether
this is necessary by checking something in /usr/include/sys/time.h;
we do not know precisely what.
AT&T 7300 or 3b1 (m68k-att-sysv)
18.52 worked. If you have strange troubles with dumping
Emacs, delete the last few lines from `src/m/7300.h' and recompile.
These lines are supposed to produce a sharable executable.
`src/m/7300.h' defines SHORTNAMES because operating system versions
older than 3.5 did not support long symbol names. Version 3.5 does
support them, so you can remove the #define SHORTNAMES in that
version.
Bull DPX/2 models 2nn or 3nn (m68k-bull-sysv3)
Minor fixes merged into 19.19, which should work with CC or GCC.
You should compile with all the POSIX stuff: undef _SYSV and define
_POSIX_SOURCE, _XOPEN_SOURCE and _BULL_SOURCE.
On bos2.00.45 there is a bug that makes the F_SETOWN fcntl
call enters in an infinite loop. F_SETOWN_BUG has been defined to avoid
calling it.
Bull DPX/20 (rs6000-bull-bosx)
Version 19 works.
Bull sps7 (m68k-bull-sysv2)
Changes partially merged in version 19, but some fixes are probably required.
CCI 5/32, 6/32
See "Tahoe".
Celerity (celerity-celerity-bsd4.2)
Version 18.49 worked. This configuration name is a hack, because we
don't know the processor used by Celerities. If someone
who uses a Celerity could get in touch with us, we can teach
config.sub a better name for the configuration.
Clipper (clipper-???)
Version 19 has support for some brand of clipper system. If you
have successfully built Emacs 19 on some sort of clipper system, let
us know so we can flesh out this entry.
Note that the Orion 105 is also a clipper, but some system-related
parameters are different.
Convex (c1-convex-bsd, c2-convex-bsd, c32-convex-bsd, c34-convex-bsd,
c38-convex-bsd)
Support updated and residual bugs fixed in 19.26.
Cubix QBx/386 (i386-cubix-sysv)
Changes merged in 19.1. Systems before 2/A/0 may fail to compile etags.c
due to a compiler bug.
Cydra 5 (cydra-cydrome-sysv)
18.51 worked in one version of their operating system but stopped
working in a newer version. This has not been fixed.
Data General Aviion (m88k-dg-dgux)
19.23 works; however, the GCC provided with DGUX 5.4R3.00 fails to
compile src/emacs.c. GCC 2.5.8 does work.
The 19.26 pretest was reported to work; no word on which compiler.
System versions other than DGUX 5.4R3.00 have not been tested.
DGUX 5.4R3.10 works with 19.29 and 19.30.
DGUX R4.11 contains changes to the stdio internals and it doesn't work
with versions before 20.2 without patches. 20.2 works in interactive
mode but usually fails in batch mode. The problem is that using
stderr in the dumped emacs usually leads to a segmentation fault.
Only m88k has been tested.
DECstation (mips-dec-ultrix or mips-dec-osf)
This machine is the older Mips-based DECstation.
Emacs should now work on the Alpha CPU.
19.25 works on Ultrix 4.2. The 19.26 pretest was reported to work
on Ultrix 4.2a and on 4.4.
One user reported 19.25 did not work at all with --with-x-toolkit
using X11R5 patch level 10, but worked ok with X11R5 pl26.
See under Ultrix for problems using X windows on Ultrix.
Note that this is a MIPS machine.
For Ultrix versions 4.1 or earlier, you may need to define
SYSTEM_MALLOC in `src/m/pmax.h', because XvmsAlloc.o in libX11.a seems
to insist on defining malloc itself.
For Ultrix versions prior to 4.0, you may need to delete
the definition of START_FILES from `src/m/pmax.h'.
Motorola Delta 147 (m68k-motorola-sysv)
The EMacs 19.26 pretest was reported to work.
Motorola Delta boxes running System V/68 release 3.
Tested on 147 board with SVR3V7, no X and gcc.
Tested on 167 board with SVR3V7, no X, cc, gnucc and gcc.
Reports say it works with X too.
The installation script chooses the compiler itself. gnucc is
preferred.
Motorola Delta 187 (m88k-motorola-sysv,
m88k-motorola-sysvr4, or
m88k-motorola-m88kbcs)
The 19.26 pretest was reported to run on SVR3. However, if you
use --with-x-toolkit on svr3, you will have problems compiling some
files because time.h and sys/time.h get included twice.
One fix is to edit those files to protect against multiple inclusion.
As of version 19.13, Emacs was reported to run under SYSVr3 and SYSVr4.
Dual running System V (m68k-dual-sysv)
As of 17.46, this worked except for a few changes
needed in unexec.c.
Dual running Uniplus (m68k-dual-uniplus)
Worked, as of 17.51.
Elxsi 6400 (elxsi-elxsi-sysv)
Changes for 12.0 release are in 19.1.
Dumping should work now.
Encore machine (ns16k-encore-bsd)
This machine bizarrely uses 4.2BSD modified to use the COFF format
for object files. Works (as of 18.40). For the APC processor you
must enable two lines at the end of `src/s/umax.h', which are commented
out in the file as distributed.
WARNING: If you compile Emacs with the "-O" compiler switch, you
must also use the "-q enter_exits" switch so that all functions have
stack frames. Otherwise routines that call `alloca' all lose.
A kernel bug in some system versions causes input characters to be lost
occasionally.
Fujitsu DS/90 (sparc-fujitsu-sysv4)
Changes merged in 20.3.
GEC 63 (local-gec63-usg5.2)
Changes are partially merged in version 18, but certainly require
more work. Let us know if you get this working, and we'll give it a
real configuration name.
Gould Power Node (pn-gould-bsd4.2 or pn-gould-bsd4.3)
18.36 worked on versions 1.2 and 2.0 of the operating system.
On UTX/32 2.0, use pn-gould-bsd4.3.
On UTX/32 1.2 and UTX/32S 1.0, use pn-gould-bsd4.2 and note that
compiling `lib-src/sorted-doc' tickles a compiler bug: remove the -g
flag to cc in the makefile.
UTX/32 1.3 has a bug in the bcopy library routine. Fix it by
#undef BSTRING in `src/m/gould.h'.
Version 19 incorporates support for releases 2.1 and later of UTX/32.
A site running a pre-release of 2.1 should #define RELEASE2_1 in config.h.
Gould NP1 (np1-gould-bsd)
Version 19 supposedly works.
Harris Night Hawk (m68k-harris-cxux or m88k-harris-cxux)
This port was added in 19.23. The configuration actually tested was
a Night Hawk 4800 running CX/UX 7.0.
If you have GCC ported and want to build with it, you probably need to
change things (like compiler switches) defined in the s/cxux.h file.
If you have X11R6 installed in /usr/lib, configure will fail to find
it and may find X11R5 instead. To work around this problem, use
--x-libraries=/usr/lib when you run configure.
With CX/UX 7.0 and later releases, you need to build after setting the
SDE_TARGET environment variable to COFF (a port using ELF and shared
libraries has not yet been done).
Harris Power PC (powerpc-harris-powerunix)
Patches have been merged in 19.31.
Honeywell XPS100 (xps100-honeywell-sysv)
Config file added in version 19.
Hewlett-Packard 9000 series 200 or 300 (m68k-hp-bsd or m68k-hp-hpux
or m68k-hp-netbsd)
These machines are 68000-series CPUs running HP/UX
(a derivative of sysV with some BSD features) or BSD 4.3 ported by Utah.
The operating system suffix determines which system Emacs is built for.
Series 200 HPUX runs Emacs only if it has the "HP/UX upgrade".
Version 19 works under BSD. The 19.26 pretest was reported
to work on HPUX 9. 19.31 works on HPUX 10.01, but there are
some problems on 10.10 which have not been resolved. Emacs 19.34
works on HPUX 10.20 provided you compile with GCC; with the HP C
compiler, subprocess commands do not work.
On HPUX 9, Emacs sometimes crashes with SIGBUS or SIGSEGV after you
delete a frame. We think this is due to a bug in the X libraries
provided by HP. With the alternative X libraries in
/usr/contrib/mitX11R5/lib, the problem does not happen.
If you are running HP/UX release 8.0 or later, you need the optional
"C/ANSI C" software in order to build Emacs (older releases of HP/UX
do not require any special software). If the file "/etc/filesets/C"
exists on your machine, you have this software, otherwise you do not.
Note that HP has used two incompatible assembler syntaxes,
and has recently changed the format of C function frames.
`src/crt0.c' and `src/alloca.s' have been conditionalised for the new
assembler and new function-entry sequence. You may need to define
OLD_HP_ASSEMBLER if you are using an older hpux version. If you
have an official (bought from HP) series 300 machine you have
the new assembler. Kernels that are 5.+ or later have new
assembler. A Series 200 that has been upgraded to a 68010
processor and a 5.+ kernel has the new compiler.
Define C_SWITCH_MACHINE to be +X to make a version of Emacs that
runs on both 68010 and 68020 based HP/UX's.
Define HPUX_68010 if you are using the new assembler, for
a system that has a 68010 without a 68881. This is to say,
a s200 (upgraded) or s310.
Define the symbol HPUX_NET if you have the optional network features
that include the `netunam' system call. This is referred to as
Network Services (NS/9000) in HP literature.
HP 9000 series 500: not supported.
The series 500 has a seriously incompatible memory architecture
which relocates data in memory during execution of a program,
and support for it would be difficult to implement.
HP 9000 series 700 or 800 (Spectrum) (hppa1.0-hp-hpux or hppa1.1-hp-hpux
or ...hpux9shr, or ...-nextstep)
Use hppa1.1 for the 700 series and hppa1.0 for the 800
series machines. (Emacs may not actually care which one you use.)
Support for NextSTEP was added in 19.31.
Emacs 20 may work on HPUX 10. You need patch PHSS_6202 to install
the Xaw and Xmu libraries. On HPUX 10.20 you may need to compile with GCC;
when Emacs was compiled with HP's C compiler, HP92453-01 A.10.32.03,
the subprocess features failed to work.
19.26 is believed to work on HPUX 9 provided you compile with GCC.
As of version 19.16, Emacs was reported to build (using GCC) and run
on HP 9000/700 series machines running HP/UX versions 8.07 and 9.01.
The HP compiler is known to fail on some versions if you use +O3,
but it may work with lower optimization levels.
Use hppa1.1-hp-hpux9shr to use shared libraries on HPUX version 9.
You may need to create the X libraries libXaw.a and libXmu.a from
the MIT X distribute, and you may need to edit src/Makefile's
definition of LIBXT to look like this:
LIBXT= $(LIBW) -lXmu -lXt $(LIBXTR6) -lXext
Some people report trouble using the GNU memory allocator under
HP/UX version 9. The problems often manifest as lots of ^@'s in the
buffer.
We are told that these problems go away if you obtain the latest
patches for the HP/UX C compiler. James J Dempsey
<jjd@spserv.bbn.com> says that this set of versions works for him:
/bin/cc:
HP92453-01 A.09.28 HP C Compiler
/lib/ccom:
HP92453-01 A.09.28 HP C Compiler
HP-UX SLLIC/OPTIMIZER HP-UX.09.00.23 02/18/93
Ucode Code Generator - HP-UX.09.00.23.5 (patch) 2/18/93
For 700 series machines, the HP-UX patch needed is known as
PHSS_2653. (Perhaps for 800 series machines as well; we don't
know.) If you are on the Internet, you should be able to obtain
this patch by using telnet to access the machine
support.mayfield.hp.com and logging in as "hpslreg" and following
the instructions there. Or you may be able to use this
web site:
HP Patch Server: http://support.mayfield.hp.com/patches/html/patches.html
HP Support Line: http://support.mayfield.hp.com
Please do not ask FSF for further support on this. If you have any
trouble obtaining the patch, contact HP Software Support.
If your buffer fills up with nulls (^@) at some point, it could well
be that problem. That problem does not happen when people use GCC
to compile Emacs. On the other hand, the HP compiler version 9.34
was reported to work for the 19.26 pretest. 9.65 was also reported to work.
If you turn on the DSUSP character (delayed suspend),
Emacs 19.26 does not know how to turn it off on HPUX.
You need to turn it off manually.
If you are running HP/UX release 8.0 or later, you need the optional
"C/ANSI C" software in order to build Emacs (older releases of HP/UX
do not require any special software). If the file "/etc/filesets/C"
exists on your machine, you have this software, otherwise you do not.
High Level Hardware Orion (orion-highlevel-bsd)
This is the original microprogrammed hardware.
Machine description file ought to work.
High Level Hardware Orion 1/05 (clipper-highlevel-bsd)
Changes merged in 18.52. This is the one with the Clipper cpu.
Note that systems which lack NFS need LOAD_AVE_TYPE changed to `double'.
C compiler has a bug; it loops compiling eval.c.
Compile it by hand without optimization.
HITACHI SR2001/SR2201 series (hppa1.1-hitachi-hiuxwe2)
These machines are based on PA architecture running HI-UX/MPP
(based on OSF1. `MPP' stands for `Massively Parallel Processor').
Emacs 19.34 is believed to work; its pretest was tested
both on SR2001 (output of `uname -rv' is `00-01-BB 0') and
SR2201 (`02-00 0').
Emacs 20.7 was reported to build on a system whose `uname -rs'
output is `HI-UX/MPP 03-04'.
The machine description file is `src/m/sr2k.h' is based on
`src/m/hp800.h'. The system description file is `src/s/hiuxwe2.h'
based on `src/s/osf1.h'. Note that this system doesn't use COFF.
IBM PS/2 (i386-ibm-aix1.1 or i386-ibm-aix1.2)
Changes merged in version 19. You may need to copy
/usr/lib/samples/hft/hftctl.c to the Emacs src directory.
i386-ibm-aix1.1 may not work with certain new X window managers, and
may be suboptimal.
IBM RS/6000 (rs6000-ibm-aix*)
Emacs 19.26 is believed to work; its pretest was tested.
Compiling with the system's `cc' and CFLAGS containing `-O5' might
fail because libXbsd isn't found. This is a compiler bug;
re-configure Emacs so that it isn't compiled with `-O5'.
At last report, Emacs didn't run well on terminals. Informed
persons say that the tty VMIN and VTIME settings have been
corrupted; if you have a fix, please send it to us.
Compiling with -O using the IBM compiler has been known
to make Emacs work incorrectly. It's reported that on
AIX 3.2.5 with an IBM compiler earlier than 1.03.00.14,
cc -O fails for some files. You need to install any
PTF containing APAR #IX42810 to bring the compiler to
the 1.03.00.14 level to allow optimized compiles.
There are reports that IBM compiler versions earlier than 1.03.00.02
fail even without -O. However, another report said that compiler
version 1.02.01.00 did work, on AIX 3.2.4, with Emacs 19.31.
As of 19.11, if you strip the Emacs executable, it ceases to work.
If you are using AIX 3.2.3, you may get a core dump when loading
ange-ftp. You may be able to fix the problem by defining LIBS_TERMCAP
as -ltermcap -lcurses. Please tell us if this fails to work.
If anyone can fix the above problems, or confirm that they don't happen
with certain versions of various programs, we would appreciate it.
IBM RT/PC (romp-ibm-bsd or romp-ibm-aix)
Use romp-ibm-bsd for the 4.2-like system and romp-ibm-aix for AIX.
19.22 is reported to work under bsd. We don't know about AIX.
On BSD, if you have trouble, try compiling with a different compiler.
On AIX, the file /usr/lib/samples/hft/hftctl.c must be compiled into
hftctl.o, with this result left in the src directory (hftctl.c is
part of the standard AIX distribution).
window.c must not be compiled with -O on AIX.
Integrated Solutions `Optimum V' (m68k-isi-bsd4.2 or -bsd4.3)
18.52 said to work on some sort of ISI machine.
Version 18.45 worked (running on a Optimum V (VME bus, 68020)
BSD 4.2 (3.05e) system). 18.42 is reported to work on
a Qbus 68010 system. Has not been tried on `WorkStation' `Cluster
Compute Node' `Cluster WorkStation' or `Server Node' (Love the
StudLYCaps)
Compilation with -O is rumored to break something.
On recent system versions, you may need to undefine the macro UMAX
in `lib-src/loadst.c' and `src/getpagesize.h'. They stupidly defined this
in a system header file, which confuses Emacs (which thinks that UMAX
indicates the Umax operating system).
Intel 386 (i386-*-isc, i386-*-esix, i386-*-bsdi2,
i386-*-xenix, i386-*-freebsd, i386-*-linux-gnu,
i386-*-sol2.4, i386-*-sysv3, i386-intsys-sysv,
i386-*-sysv4, i386-*-sysv4.2,
i386-*-sysv5.3, i386-*-bsd4.2,
i386-*-sco3.2v4, i386-*-bsd386, i386-*-386bsd,
i386-*-msdos, i386-*-windowsnt.
i386... can be replaced with i486... or i586...)
In the above configurations, * means that the manufacturer's name
you specify does not matter, and you can use any name you like
(but it should not contain any dashes or stars).
When using the ISC configurations, be sure to specify the isc
version number - for example, if you're running ISC 3.0, use
i386-unknown-isc3.0 as your configuration name.
Use i386-*-esix for Esix; Emacs runs as of version 19.6.
Use i386-*-linux-gnu for GNU/Linux systems; Emacs runs as of version 19.26.
Use i386-intsys-sysv for Integrated Solutions 386 machines.
It may also be correct for Microport systems.
Use i386-*-sco3.2v4 for SCO 3.2v4; Emacs runs as of version 19.26.
On GNU/Linux systems, Emacs 19.23 was said to work properly with libc
version 4.5.21, but not with 4.5.19. If your system uses QMAGIC
for the executable format, you must edit config.h to define LINUX_QMAGIC.
On GNU/Linux, configure may fail to put these definitions in config.h:
#define HAVE_GETTIMEOFDAY
#define HAVE_MKDIR
#define HAVE_RMDIR
#define HAVE_XSCREENNUMBEROFSCREEN
To work around the problem, add those definitions by hand.
It is possible that this problem happens only with X11R6.
Newer system versions have fixed it.
The 19.26 pretest was reported to work on SVR4.3 and on Freebsd.
19.29 is reported to crash when using Motif on Solaris 2.5.
The reasons are not yet known.
Use i386-*-bsdiN for BSDI BSD/OS version N; Emacs runs as of version 19.23.
In some system versions, `make' is broken; use GNU make instead.
Shell bugs in version 1.0 of BSD/OS cause configure
to do the wrong thing with --with-x-toolkit; the workaround is to edit
configure to run another shell such as bash.
For System V release 3, use i386-*-sysv3.
For System V release 4, use i386-*-sysv4.
For System V release 4.2, use i386-*-sysv4.2.
If you are using Xenix, see notes at end under Xenix.
If you are using Esix, see notes at end under Esix.
If you are using SCO Unix, see notes at end under SCO.
On 386bsd, NetBSD and FreeBSD, at one time, it was necessary to use
GNU make, not the system's make. Assuming it's installed as gmake,
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
requires including `/usr/src/linux/include/linux' in buffer.c
but no coherent explanation of why that might be so. If it is so,
in current versions of Linux, something else should probably be changed.
Some sysV.3 systems seem to have bugs in `opendir';
for them, alter `config.h' to define NONSYSTEM_DIR_LIBRARY
and undefine SYSV_SYSTEM_DIR.
If you use optimization on V.3, you may need the option -W2,'-y 0'
to prevent certain faulty optimization.
On 386/ix, to link with shared libraries, add #define USG_SHARED_LIBRARIES
to config.h.
On SCO, there are problems in regexp matching when Emacs is compiled