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
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
C compiler has a bug; it loops compiling eval.c.
Compile it by hand without optimization.
-HITACHI SR2001/SR2201 series (hppa1.1-hitachi-hiuxmpp)
+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/hiuxmpp.h'
+ `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)
fail because libXbsd isn't found. This is a compiler bug;
re-configure Emacs so that it isn't compiled with `-O5'.
+ On AIX 4.3.x and 4.4, compiling with /bin/c89 fails because it
+ treats certain warnings as errors. Use `cc' instead.
+
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.
window.c must not be compiled with -O on AIX.
+IBM System/390 running GNU/Linux (s390-*-linux-gnu)
+
+ As of Emacs 21.2, a 31-bit only version is supported on this
+ system.
+
Integrated Solutions `Optimum V' (m68k-isi-bsd4.2 or -bsd4.3)
18.52 said to work on some sort of ISI machine.
flag or otherwise (see cc(1)). This may work on earlier Irix 6
systems if you edit src/s/irix6-0.h following irix6-5.h.
+ Building Emacs 21.1 and 21.2 on versions of Irix before 6.5.10,
+ especially when Emacs is built with GCC, was reported to have subtle
+ problems such as being unable to print to stdout under the -batch
+ command-line option. Building with the native compiler or upgrading
+ the OS to a newer version solves these problems. There's evidence
+ that these problems are actually related to the runtime libraries
+ (before IRIX 6.5.10, the IRIX runtimes were based on the MIPSpro 7.2
+ compilers), so installing patches for the runtime from
+ http://www.sgi.com/support/patch_intro.html could solve the problem
+ even without upgrading the OS. The dump process is the crucial
+ step that needs the upgraded runtime, so a workaround is to dump
+ Emacs on a machine with a newer OS, then copy the binary to the
+ older OS.
+
If compiling with GCC on Irix 6 yields an error "conflicting types
for `initstate'", install GCC 2.95 or a newer version, and this
problem should go away. It is possible that this problem results
including large file support) on a Solaris system which supports
64-bit executables, use the Sun compiler, configuring something like
this (see the cc documentation for information on 64-bit
- compilation): env CC="cc -xarch=v9" ./configure --without-gcc
+ compilation): env CC="cc -xarch=v9" ./configure
As of version 2.95, GCC doesn't support the 64-bit ABI properly, but
later releases may.
+ Some versions of Solaris 8 have a bug in their XIM (X Input Method)
+ implementation which causes Emacs to dump core when one of several
+ frames is closed. To avoid this, either install patch 108773-12
+ (for Sparc) or 108874-12 (for x86), or configure Emacs with the
+ `--with-xim=no' switch (you can use Leim input methods instead).
+
On 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
another system with Solaris 8 using apparently the same 5.0 compiler
and the default CFLAGS.
+ Emacs 21.1 and 21.2 built with Sun's ProWorks PC3.0.1 compiler on
+ Intel/Solaris 8 was reported to abort and dump core during startup.
+ Using GCC or a newer SUN compiler (Sun WokShop 6 update 2 C 5.3
+ 2001/05/15) solves the problem.
+
Emacs 20.5 and later work on SPARC GNU/Linux with the 32-bit ABI.
As of release 2.95, GCC doesn't work properly with the 64-bit ABI
(applicable on UltraSPARC), but that isn't the default mode.
distribution. See the file ../vms/VMSINSTALL for info on moving
Unix distributions to VMS, and other VMS-related topics.
-Windows NT
+Windows NT/95/98/ME/2000
- For installation on Windows NT, see the file etc/INSTALL and search for
- `Windows NT'.
+ For installation on all versions of the MS-Windows platform, see the
+ file nt/INSTALL.
Xenix (xenix)
HCoop / bpt / emacs.git / blobdiff