home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Fresh Fish 2
/
FFMCD02.bin
/
useful
/
lib
/
emacs
/
18.59
/
etc
/
machines
< prev
next >
Wrap
Text File
|
1992-10-29
|
31KB
|
885 lines
This is a list of the status of GNU Emacs on various machines and systems.
Last updated 18 Oct 1992.
Systems:
For each type of system, the name of the appropriate s- header file
is given.
Berkeley 4.1 (s-bsd4-1.h)
Works on vaxes.
Berkeley 4.2 (s-bsd4-2.h)
Works on several machines.
Berkeley 4.3 (s-bsd4-3.h)
Works, on Vaxes at least.
Microport
See under "Intel 386".
Solaris (s-sol2.h)
Changes merged, and may work.
System V rel 0 (s-usg5-0.h)
Works, on Vaxes and 3bxxx's.
There are some problems in 18.37 due to shortnames/cccp problems:
use the emacs 17 cpp if you have it.
System V rel 2 (s-usg5-2.h)
Works on various machines.
On some (maybe all) machines the library -lPW exists and contains
a version of `alloca'. On these machines, to use it, put
#define HAVE_ALLOCA
#define LIB_STANDARD -lPW -lc
in the m-...h file for the machine.
If you find that the character Meta-DEL makes Emacs crash,
find where function init_sys_modes in sysdep.c sets sg.c_cc[VQUIT]
and make it store 7 there. I have as yet no evidence of whether
this problem, known in HP-UX, exists in other system V versions.
If you are compiling to work with X11 release 4, you may need
to define HAVE_RANDOM in config.h.
System V rel 2.2 (s-usg5-2-2.h)
In 5.2.2 AT&T undid, incompatibly, their previous incompatible
change to the way the nlist library is called. A different s- file
is used to enable the other interface.
They call themselves the right choice--can't they choose?
Emacs version 18 unexec is currently not working properly
on 5.2.2. Nobody knows why yet. A workaround is to define
NO_REMAP. It is not yet known whether this applies to all
machines running 5.2.2.
If you are compiling to work with X11 release 4, you may need
to define HAVE_RANDOM in config.h.
System V rel 3 (s-usg5-3.h)
Some versions of this system support ptys and BSD-style sockets.
On such systems, you should define HAVE_PTYS and HAVE_SOCKETS in config.h.
If you are compiling to work with X11 release 4, you may need
to define HAVE_RANDOM in config.h.
If you want to link Emacs with shared libraries, define
USG_SHARED_LIBRARIES.
System V rel 4 (s-usg5-4.h)
Supported, including shared libraries for ELF. pty's work now.
The standard C preprocessor generates xmakefile incorrectly. However,
/lib/cpp will work, so use `make CPP=/lib/cpp' in the `src' subdirectory.
Versions 3 and earlier of V.4, on the Intel 386 and 860, had
problems in the X11 libraries. These prevent Emacs from working
with X. You can use Emacs with X provided your copy of X is based
on X11 release 4 or newer. Unfortunately, the only way you can tell
for certain whether your X11 library is new enough is to try
compiling Emacs to use X. If xemacs runs, your X11 library is new
enough.
In this context, GSV4 and GSV4i are alternate names for X11R4.
OL2.* is X11R3 based. OL3 is in between X11R3 and X11R4, and may or
may not work, depending on who made the Unix system. If the library
libXol is part of the X distribution, then you have X11R3 and Emacs
won't work with X.
Most versions of V.4 support sockets. If `/usr/lib/libsocket.so'
exists, your system supports them. If yours does not, you must add
#undef HAVE_SOCKETS in config.h, aftern the inclusion of s-usg5-4.h.
(Any system that supports Internet should implement sockets.)
Ultrix (s-bsd4-3.h)
Recent versions of Ultrix appear to support the features of Berkeley 4.3.
Ultrix was at the BSD 4.2 level for a long time after BSD 4.3 came out.
Ultrix 3.0 has incompatibilities in its X library if you have the
Ultrix version of X (UWS version 2.0). To solve them, you need to
prevent XvmsAlloc.o in Xlib from being used. Israel Pinkas says:
I added the following lines to config.h after the X defines:
#if defined(ultrix) && defined(X11)
#define OBJECTS_SYSTEM calloc.o
#endif
Then I ran the following:
ar x /usr/lib/libc.a calloc.o
The problem is said to be gone in UWS version 2.1.
Ultrix 4.1 has moved the file X11/X10.h into mit/X11/X10.h.
Uniplus 5.2 (s-unipl5-2.h)
Works, on Dual machines at least.
VMS (s-vms4-0.h, s-vms4-2.h, s-vms4-4.h, s-vms5-5.h)
Works except for certain features (directory listing, dired,
sending and receiving mail) that use synchronous subprocesses.
(These will work in Emacs 19.)
s-vms5-5.h may be right for some earlier versions; please let us know
what happens when you try it in VMS versions 5.0 thru 5.4.
Note that Emacs for VMS is usually distributed in a special
VMS distribution. See the file ../VMSINSTALL for info on moving
Unix distributions to VMS, and other VMS-related topics.
Xenix
Should work in 18.50, but you will need to edit the files
etc/Makefile and src/ymakefile
(see the comments that mention "Xenix" for what to change.)
Compiling Emacs with -O is said not to work.
If you want Emacs to work with Smail (installed as /usr/bin/smail)
then add the line #define SMAIL to config.h.
The file etc/XENIX suggests some useful things to do to Xenix
to make the Emacs meta key work.
Machines:
For each type of machine, the names of the m- and s- header files
are given.
Alliant FX/80 (m-alliant4.h or m-alliant.h or m-alliant1.h;
s-bsd4-2.h or s-bsd4-3.h)
There are reports of bugs in the Alliant compiler
that prevent compiling Emacs 18.57.
No word on how to get around them. Perhaps using GCC will work.
A work-around is installed in src/dispnew.c in 18.58 for a compiler bug.
18.52 worked on system version 4. Previous Emacs versions were
known to work on previous system versions.
Use m-alliant1.h on version 1 of their operating system
and use m-alliant.h on version 2 or 3.
Use m-alliant4.h on version 4 and above.
Use s-bsd4-3.h with system version 5 and above.
Alliant FX/2800 (m-all2800.h; s-bsd4-3.h)
Known to work with 18.58 and OS version 2.2, compiler version 1.3.
Altos 3068 (m-altos.h; s-usg5-2.h)
18.52 is said to work, provided you don't compile unexec.c with -O.
Amdahl UTS (m-amdahl.h; s-usg5-3.h)
Support for a newer system version, and X Windows, merged in 18.58.
(Some people report that s-usg5-2.h worked better than s-usg5-3.h
for 18.57.)
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.
Apollo running Domain (m-apollo.h; s-bsd4-2.h)
18.52 works, to some extent.
Code for dumping Emacs has been written, but we cannot
distribute it yet.
There are reports of bugs in cc -O on this system.
In etc/Makefile, don't expect emacsclient and server to
compile. You might want to remove them from your makefile.
Supposedly something in dired.c runs into a compiler bug.
Paraphrasing the statement should avoid the problem.
I havenot yet received word as to the exact statement this is.
AT&T 3b2, 3b5, 3b15, 3b20 (m-att3b.h; s-usg5-2-2.h)
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. If it's too small,
you can perhaps fix it using the file `ulimit.hack' in this directory.
Note that for V.3.1 and later releases, 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. Do not use ulimit.hack if you have V.3.1 or later.
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.
AT&T 7300 or 3b1 (m-7300.h; s-usg5-2-2.h)
18.52 seems to work. If you have strange troubles with dumping Emacs,
delete the last few lines from m-7300.h and recompile. These lines
are su