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.
+ 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
even worth trying to use it. Success was obtained with the
uts native C compiler on uts version 5.2.5.
+Apple Macintosh running Mac OS X
+
+ For installation on all versions of the Mac OS platform, see the file
+ mac/INSTALL.
+
+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
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.
-
+ 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
AT&T 3b2, 3b5, 3b15, 3b20 (we32k-att-sysv)
- Emacs will probably not work with certain kernel constants too small.
+ 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
+ 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
_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
+ call enters in an infinite loop. F_SETOWN_BUG has been defined to avoid
calling it.
Bull DPX/20 (rs6000-bull-bosx)
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
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
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
+ 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.
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
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:
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
+ both on SR2001 (output of `uname -rv' is `00-01-BB 0') and
SR2201 (`02-00 0').
-
- 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'
- based on `src/s/osf1.h'. Note that this system doesn't use COFF.
+
+ 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)
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'.
+
+ 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.
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)
+ StudLYCaps)
Compilation with -O is rumored to break something.
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-*-sysv5.3, i386-*-bsd4.2, i386-*-cygwin,
i386-*-sco3.2v4, i386-*-bsd386, i386-*-386bsd,
i386-*-msdos, i386-*-windowsnt.
i386... can be replaced with i486... or i586...)
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-*-cygwin for Cygwin; Emacs builds as of version 22.1, in both X11
+ and non-X11 modes. (The Cygwin site has source and binaries for 21.2.)
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.
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
Iris 4D (mips-sgi-irix[456].*)
+ Emacs 21.3 is reported to work on IRIX 6.5.x.
+
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
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.
- The 19.26 pretest was reported to work on IRIX 4.0.5 and 5.2.
- 19.23 was reported to work on IRIX 5.2, but you may need to install
- the "compiler_dev.hdr.internal" subsystem in order to compile unexelfsgi.c.
- 19.22 was known to work on all Silicon Graphics machines running
- IRIX 4.0.5 or IRIX 5.1.
-
- Compiling with -O using IRIX compilers prior to 3.10.1 may not work.
- Don't use -O or use GCC instead.
-
- Most IRIX 3.3 systems do not have an ANSI C compiler, but a few do.
- Compile Emacs 18 with the -cckr switch on these machines.
-
- There is a bug in IRIX 3.3 that can sometimes leave ptys owned by root
- with a permission of 622. This causes malfunctions in use of
- subprocesses of Emacs. Irix versions 4.0 and later with GNU Emacs
- versions 18.59 and later fix this bug.
+ 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
+ from upgrading the operating system without reinstalling GCC; so you
+ could also try reinstalling the same version of GCC, and telling us
+ whether that fixes the problem.
Masscomp (m68k-masscomp-rtu)
was reported for 18.36 on a Masscomp (model and version unknown but probably
a 68020 system). The report sounds like a compiler bug.
- A compiler bug affecting statements like
+ A compiler bug affecting statements like
unsigned char k; unsigned char *p;... x = p[k];
has been reported for "C version 1.2 under RTU 3.1". We do not wish
to take the time to install the numerous workarounds required to
You need to build Emacs in the Berkeley universe with
the `ucb' command, as in `ucb make' or `ucb build-install'.
-
+
In OSx 4.0, it seems necessary to add the following two lines
to `src/m/pyramid.h':
#define _longjmp longjmp
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
+ 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.
+
+ 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.
19.32 works on Solaris 2.4 and 2.5. On Solaris 2.5
you may need one of these patches to prevent Emacs from crashing
when it starts up:
- 103093-03: [README] SunOS 5.5: kernel patch (2140557 bytes)
- 102832-01: [README] OpenWindows 3.5: Xview Jumbo Patch (4181613 bytes)
+ 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)
There are reports that using SunSoft cc with -xO4 -xdepend produces
`sparc-sun-sunos4.1'. For SunOS release 4.1.3 on a Sparc, use
`sparc-sun-sunos4.1.3'. Note that shared libraries are now
used by default on SunOS 4.1.
-
+
A user reported irreproducible segmentation faults when using 19.29
on Solaris 2.3 and 2.4 after compiling it with the Sun compiler.
The problem went away when GCC 2.7.0 was used instead. We do not know
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)
mode: indented-text
fill-prefix: " "
End:
+
+
+arch-tag: 7d2e93c7-e982-40ec-9055-3cd064042473