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  with the system compiler.  The compiler version is "Microsoft C  version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93;  Quick C Compiler Version 1.00.46 (Beta).  The solution is to compile  with GCC.  On ISC systems (2.02 and more recent), don't try to use the versions  of X that come with the system; use XFree86 instead.  There is no consistency in the handling of certain system header files  on V.3.  Some versions have sys/sioctl.h, and require it in sysdep.c.  But some versions do not have sys/sioctl.h.  For a given version of the system, this may depend on whether you have  X Windows or TCP/IP.  Define or undefine NO_SIOCTL_H in config.h  according to whether you have the file.  Likewise, some versions have been known to need sys/ttold.h, sys/stream.h,  and sys/ptem.h included in sysdep.c.  If your system has these files,  try defining NEED_PTEM_H in config.h if you have trouble without it.  You may find that adding -I/usr/X/include or -I/usr/netinclude or both  to CFLAGS avoids compilation errors on certain systems.  Some versions convince sysdep.c to try to use `struct tchars'  but define `struct tc' instead; add `#define tchars tc'  to config.h to solve this problem.Iris 2500 and Iris 2500 Turbo (m68k-sgi-iris3.5 or m68k-sgi-iris3.6)  Version 18 was said to work; use m68k-sgi-iris3.5 for system version 2.5  and m68k-sgi-iris3.6 for system version 3.6.  Note that the 3030 is the same as the Iris 2500 Turbo.Iris 4D (mips-sgi-irix[456].*)  You can build a 64-bit executable (with larger maximum buffer size)  on Irix 6.5 by specifying the 64-bit ABI using the `-64' compiler