+The compiler was reported to crash while compiling syntax.c with the
+following message:
+
+ cc: Internal compiler error: program cc1obj got fatal signal 11
+
+To work around this, replace the macros UPDATE_SYNTAX_TABLE_FORWARD,
+INC_BOTH, and INC_FROM with functions. To this end, first define 3
+functions, one each for every macro. Here's an example:
+
+ static int update_syntax_table_forward(int from)
+ {
+ return(UPDATE_SYNTAX_TABLE_FORWARD(from));
+ }/*update_syntax_table_forward*/
+
+Then replace all references to UPDATE_SYNTAX_TABLE_FORWARD in syntax.c
+with a call to the function update_syntax_table_forward.
+
+*** Solaris 2.x
+
+**** Strange results from format %d in a few cases, on a Sun.
+
+Sun compiler version SC3.0 has been found to miscompile part of
+editfns.c. The workaround is to compile with some other compiler such
+as GCC.
+
+**** On Solaris, Emacs dumps core if lisp-complete-symbol is called.
+
+If you compile Emacs with the -fast or -xO4 option with version 3.0.2
+of the Sun C compiler, Emacs dumps core when lisp-complete-symbol is
+called. The problem does not happen if you compile with GCC.
+
+**** On Solaris, Emacs crashes if you use (display-time).
+
+This can happen if you configure Emacs without specifying the precise
+version of Solaris that you are using.
+
+**** Solaris 2.3 and 2.4: Unpredictable segmentation faults.
+
+A user reported that this happened in 19.29 when it was compiled with
+the Sun compiler, but not when he recompiled with GCC 2.7.0.
+
+We do not know whether something in Emacs is partly to blame for this.
+
+**** Solaris 2.4: Emacs dumps core on startup.
+
+Bill Sebok says that the cause of this is Solaris 2.4 vendor patch
+102303-05, which extends the Solaris linker to deal with the Solaris
+Common Desktop Environment's linking needs. You can fix the problem
+by removing this patch and installing patch 102049-02 instead.
+However, that linker version won't work with CDE.
+
+Solaris 2.5 comes with a linker that has this bug. It is reported that if
+you install all the latest patches (as of June 1996), the bug is fixed.
+We suspect the crucial patch is one of these, but we don't know
+for certain.
+
+ 103093-03: [README] SunOS 5.5: kernel patch (2140557 bytes)
+ 102832-01: [README] OpenWindows 3.5: Xview Jumbo Patch (4181613 bytes)
+ 103242-04: [README] SunOS 5.5: linker patch (595363 bytes)
+
+(One user reports that the bug was fixed by those patches together
+with patches 102980-04, 103279-01, 103300-02, and 103468-01.)
+
+If you can determine which patch does fix the bug, please tell
+bug-gnu-emacs@gnu.org.
+
+Meanwhile, the GNU linker links Emacs properly on both Solaris 2.4 and
+Solaris 2.5.
+
+**** Solaris 2.4: Dired hangs and C-g does not work. Or Emacs hangs
+forever waiting for termination of a subprocess that is a zombie.
+
+casper@fwi.uva.nl says the problem is in X11R6. Rebuild libX11.so
+after changing the file xc/config/cf/sunLib.tmpl. Change the lines
+
+ #if ThreadedX
+ #define SharedX11Reqs -lthread
+ #endif
+
+to:
+
+ #if OSMinorVersion < 4
+ #if ThreadedX
+ #define SharedX11Reqs -lthread
+ #endif
+ #endif
+
+Be sure also to edit x/config/cf/sun.cf so that OSMinorVersion is 4
+(as it should be for Solaris 2.4). The file has three definitions for
+OSMinorVersion: the first is for x86, the second for SPARC under
+Solaris, and the third for SunOS 4. Make sure to update the
+definition for your type of machine and system.
+
+Then do `make Everything' in the top directory of X11R6, to rebuild
+the makefiles and rebuild X. The X built this way work only on
+Solaris 2.4, not on 2.3.
+
+For multithreaded X to work it is necessary to install patch
+101925-02 to fix problems in header files [2.4]. You need
+to reinstall gcc or re-run just-fixinc after installing that
+patch.
+
+However, Frank Rust <frust@iti.cs.tu-bs.de> used a simpler solution:
+he changed
+ #define ThreadedX YES
+to
+ #define ThreadedX NO
+in sun.cf and did `make World' to rebuild X11R6. Removing all
+`-DXTHREAD*' flags and `-lthread' entries from lib/X11/Makefile and
+typing 'make install' in that directory also seemed to work.
+
+**** Solaris 2.x: GCC complains "64 bit integer types not supported".
+
+This suggests that GCC is not installed correctly. Most likely you
+are using GCC 2.7.2.3 (or earlier) on Solaris 2.6 (or later); this
+does not work without patching. To run GCC 2.7.2.3 on Solaris 2.6 or
+later, you must patch fixinc.svr4 and reinstall GCC from scratch as
+described in the Solaris FAQ
+<http://www.wins.uva.nl/pub/solaris/solaris2.html>. A better fix is
+to upgrade to GCC 2.8.1 or later.
+
+**** Solaris 2.7: Building Emacs with WorkShop Compilers 5.0 98/12/15
+C 5.0 failed, apparently with non-default CFLAGS, most probably due to
+compiler bugs. Using Sun Solaris 2.7 Sun WorkShop 6 update 1 C
+release was reported to work without problems. It worked OK on
+another system with Solaris 8 using apparently the same 5.0 compiler
+and the default CFLAGS.
+
+**** Solaris 2.x: Emacs dumps core when built with Motif.
+
+The Solaris Motif libraries are buggy, at least up through Solaris 2.5.1.
+Install the current Motif runtime library patch appropriate for your host.
+(Make sure the patch is current; some older patch versions still have the bug.)
+You should install the other patches recommended by Sun for your host, too.
+You can obtain Sun patches from ftp://sunsolve.sun.com/pub/patches/;
+look for files with names ending in `.PatchReport' to see which patches
+are currently recommended for your host.
+
+On Solaris 2.6, Emacs is said to work with Motif when Solaris patch
+105284-12 is installed, but fail when 105284-15 is installed.
+105284-18 might fix it again.
+
+**** Solaris 2.6 and 7: the Compose key does not work.
+
+This is a bug in Motif in Solaris. Supposedly it has been fixed for
+the next major release of Solaris. However, if someone with Sun
+support complains to Sun about the bug, they may release a patch.
+If you do this, mention Sun bug #4188711.
+
+One workaround is to use a locale that allows non-ASCII characters.
+For example, before invoking emacs, set the LC_ALL environment
+variable to "en_US" (American English). The directory /usr/lib/locale
+lists the supported locales; any locale other than "C" or "POSIX"
+should do.
+
+pen@lysator.liu.se says (Feb 1998) that the Compose key does work
+if you link with the MIT X11 libraries instead of the Solaris X11
+libraries.
+
+*** HP/UX versions before 11.0
+
+HP/UX 9 was end-of-lifed in December 1998.
+HP/UX 10 was end-of-lifed in May 1999.
+
+**** HP/UX 9: Emacs 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.
+
+*** HP/UX 10: Large file support is disabled.
+
+See the comments in src/s/hpux10.h.
+
+*** HP/UX: Emacs is slow using X11R5.
+
+This happens if you use the MIT versions of the X libraries--it
+doesn't run as fast as HP's version. People sometimes use the version
+because they see the HP version doesn't have the libraries libXaw.a,
+libXmu.a, libXext.a and others. HP/UX normally doesn't come with
+those libraries installed. To get good performance, you need to
+install them and rebuild Emacs.
+
+*** Ultrix and Digital Unix
+
+**** Ultrix 4.2: `make install' fails on install-doc with `Error 141'.
+
+This happens on Ultrix 4.2 due to failure of a pipeline of tar
+commands. We don't know why they fail, but the bug seems not to be in
+Emacs. The workaround is to run the shell command in install-doc by
+hand.
+
+**** Digital Unix 4.0: Garbled display on non-X terminals when Emacs runs.
+
+So far it appears that running `tset' triggers this problem (when TERM
+is vt100, at least). If you do not run `tset', then Emacs displays
+properly. If someone can tell us precisely which effect of running
+`tset' actually causes the problem, we may be able to implement a fix
+in Emacs.
+
+**** Ultrix: `expand-file-name' fails to work on any but the machine you dumped Emacs on.
+
+On Ultrix, if you use any of the functions which look up information
+in the passwd database before dumping Emacs (say, by using
+expand-file-name in site-init.el), then those functions will not work
+in the dumped Emacs on any host but the one Emacs was dumped on.
+
+The solution? Don't use expand-file-name in site-init.el, or in
+anything it loads. Yuck - some solution.
+
+I'm not sure why this happens; if you can find out exactly what is
+going on, and perhaps find a fix or a workaround, please let us know.
+Perhaps the YP functions cache some information, the cache is included
+in the dumped Emacs, and is then inaccurate on any other host.
+
+*** SVr4
+
+**** SVr4: On some variants of SVR4, Emacs does not work at all with X.
+
+Try defining BROKEN_FIONREAD in your config.h file. If this solves
+the problem, please send a bug report to tell us this is needed; be
+sure to say exactly what type of machine and system you are using.
+
+**** SVr4: After running emacs once, subsequent invocations crash.
+
+Some versions of SVR4 have a serious bug in the implementation of the
+mmap () system call in the kernel; this causes emacs to run correctly
+the first time, and then crash when run a second time.
+
+Contact your vendor and ask for the mmap bug fix; in the mean time,
+you may be able to work around the problem by adding a line to your
+operating system description file (whose name is reported by the
+configure script) that reads:
+#define SYSTEM_MALLOC
+This makes Emacs use memory less efficiently, but seems to work around
+the kernel bug.
+
+*** Irix 5 and earlier
+
+Exactly when Irix-5 end-of-lifed is obscure. But since Irix 6.0
+shipped in 1994, it has been some years.
+
+**** Irix 5.2: unexelfsgi.c can't find cmplrs/stsupport.h.
+
+The file cmplrs/stsupport.h was included in the wrong file set in the
+Irix 5.2 distribution. You can find it in the optional fileset
+compiler_dev, or copy it from some other Irix 5.2 system. A kludgy
+workaround is to change unexelfsgi.c to include sym.h instead of
+syms.h.
+
+**** Irix 5.3: "out of virtual swap space".
+
+This message occurs when the system runs out of swap space due to too
+many large programs running. The solution is either to provide more
+swap space or to reduce the number of large programs being run. You
+can check the current status of the swap space by executing the
+command `swap -l'.
+
+You can increase swap space by changing the file /etc/fstab. Adding a
+line like this:
+
+/usr/swap/swap.more swap swap pri=3 0 0
+
+where /usr/swap/swap.more is a file previously created (for instance
+by using /etc/mkfile), will increase the swap space by the size of
+that file. Execute `swap -m' or reboot the machine to activate the
+new swap area. See the manpages for `swap' and `fstab' for further
+information.
+
+The objectserver daemon can use up lots of memory because it can be
+swamped with NIS information. It collects information about all users
+on the network that can log on to the host.
+
+If you want to disable the objectserver completely, you can execute
+the command `chkconfig objectserver off' and reboot. That may disable
+some of the window system functionality, such as responding CDROM
+icons.
+
+You can also remove NIS support from the objectserver. The SGI `admin'
+FAQ has a detailed description on how to do that; see question 35
+("Why isn't the objectserver working?"). The admin FAQ can be found at
+ftp://viz.tamu.edu/pub/sgi/faq/.
+
+**** Irix 5.3: Emacs crashes in utmpname.
+
+This problem is fixed in Patch 3175 for Irix 5.3.
+It is also fixed in Irix versions 6.2 and up.
+
+**** Irix 6.0: Make tries (and fails) to build a program named unexelfsgi.
+
+A compiler bug inserts spaces into the string "unexelfsgi . o"
+in src/Makefile. Edit src/Makefile, after configure is run,
+find that string, and take out the spaces.
+
+Compiler fixes in Irix 6.0.1 should eliminate this problem.
+
+*** SCO Unix and UnixWare
+
+**** SCO 3.2v4: Unusable default font.
+
+The Open Desktop environment comes with default X resource settings
+that tell Emacs to use a variable-width font. Emacs cannot use such
+fonts, so it does not work.
+
+This is caused by the file /usr/lib/X11/app-defaults/ScoTerm, which is
+the application-specific resource file for the `scoterm' terminal
+emulator program. It contains several extremely general X resources
+that affect other programs besides `scoterm'. In particular, these
+resources affect Emacs also:
+
+ *Font: -*-helvetica-medium-r-*--12-*-p-*
+ *Background: scoBackground
+ *Foreground: scoForeground
+
+The best solution is to create an application-specific resource file for
+Emacs, /usr/lib/X11/sco/startup/Emacs, with the following contents:
+
+ Emacs*Font: -*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
+ Emacs*Background: white
+ Emacs*Foreground: black
+
+(These settings mimic the Emacs defaults, but you can change them to
+suit your needs.) This resource file is only read when the X server
+starts up, so you should restart it by logging out of the Open Desktop
+environment or by running `scologin stop; scologin start` from the shell
+as root. Alternatively, you can put these settings in the
+/usr/lib/X11/app-defaults/Emacs resource file and simply restart Emacs,
+but then they will not affect remote invocations of Emacs that use the
+Open Desktop display.
+
+These resource files are not normally shared across a network of SCO
+machines; you must create the file on each machine individually.
+
+**** SCO 4.2.0: Regular expressions matching bugs on SCO systems.
+
+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.
+
+**** UnixWare 2.1: Error 12 (virtual memory exceeded) when dumping Emacs.
+
+Paul Abrahams (abrahams@acm.org) reports that with the installed
+virtual memory settings for UnixWare 2.1.2, an Error 12 occurs during
+the "make" that builds Emacs, when running temacs to dump emacs. That
+error indicates that the per-process virtual memory limit has been
+exceeded. The default limit is probably 32MB. Raising the virtual
+memory limit to 40MB should make it possible to finish building Emacs.
+
+You can do this with the command `ulimit' (sh) or `limit' (csh).
+But you have to be root to do it.
+
+According to Martin Sohnius, you can also retune this in the kernel:
+
+ # /etc/conf/bin/idtune SDATLIM 33554432 ## soft data size limit
+ # /etc/conf/bin/idtune HDATLIM 33554432 ## hard "
+ # /etc/conf/bin/idtune SVMMSIZE unlimited ## soft process size limit
+ # /etc/conf/bin/idtune HVMMSIZE unlimited ## hard "
+ # /etc/conf/bin/idbuild -B
+
+(He recommends you not change the stack limit, though.)
+These changes take effect when you reboot.
+
+*** Linux 1.x
+
+**** Linux 1.0-1.04: Typing C-c C-c in Shell mode kills your X server.
+
+This happens with Linux kernel 1.0 thru 1.04, approximately. The workaround is
+to define SIGNALS_VIA_CHARACTERS in config.h and recompile Emacs.
+Newer Linux kernel versions don't have this problem.
+
+**** Linux 1.3: Output from subprocess (such as man or diff) is randomly
+truncated on GNU/Linux systems.
+
+This is due to a kernel bug which seems to be fixed in Linux version
+1.3.75.
+
+** Windows 3.1, 95, 98, and ME
+
+*** MS-Windows NT/95: Problems running Perl under Emacs