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 shouldpass to the `configure' script to prepare to build Emacs for thatsystem/machine.The `configure' script uses the configuration name to decide whichmachine and operating system description files `src/config.h' shouldinclude.  The machine description files are all in `src/m', and havenames similar to, but not identical to, the machine names used inconfiguration names.  The operating system files are all in `src/s',and are named similarly.  See the `configure' script if you need toknow which configuration names use which machine and operating systemdescription files.If you add support for a new configuration, add a section to thisfile, and then edit the `configure' script to tell it whichconfiguration name(s) should select your new machine description andsystem description files.Here are the configurations Emacs is intended to work with, with thecorresponding configuration names.  You can postpend version numbersto operating system names (i.e. sunos4.1) or architecture names (i.e.hppa1.1).  If you leave out the version number, the `configure' scriptwill 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  DEC C compiler version 5.9 (DEC C V5.9-005 on Digital UNIX V4.0f)  is reported to produce bogus binaries of Emacs 21.2 when the  command-line switches "-O4 -arch ev6 -tune ev6" are used.  Using  just -O4 produces a good executable.  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.Apple PowerPC Macintosh running GNU/Linux  There are special considerations for a variety of this system which  is known as the ``Yellow Dog [GNU/]Linux'': Emacs may crash during  dumping.  To solve this, edit the header file src/m/macppc.h in the  Emacs distribution, and remove the "#if 0" and "#endif" directives  which surround the following block near the end of the file:    #if 0  /* This breaks things on PPC GNU/Linux ecept for Yellowdog,	      even with identical GCC, as, ld.  Let's take it out until we	      know what's really going on here.  */    /* GCC 2.95 and newer on GNU/Linux PPC changed the load address to       0x10000000.  */    #if defined __linux__    #if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 95)    #define DATA_SEG_BITS  0x10000000    #endif    #endif    #endif /* 0 */  After that, reconfigure and rebuild Emacs.  It should now build  successfully.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'.