Commit a7bfd66f authored by Dave Love's avatar Dave Love


parent 5bcd0f1e
[Someone sent this in from California, and we decided to extend
our campaign against information hoarding to recipes as well
as software. (Recipes are the closest thing, not involving computers,
to software.)
The story appears to be a myth, according to the Chicago Tribune,
which says that Mrs Fields Cookies hoards the information completely.
Therefore, this recipe can be thought of as a compatible replacement.
We have reports that the cookies it makes are pretty good.]
Someone at PG&E called the Mrs. Fields Cookie office
and requested the recipe for her cookies. They asked
her for her charge card number, and she gave it to them
thinking the cost would be $15 to $25. It turned out
to be $200!
Therefore, this person is giving the recipe to anyone
and everyone she knows (and doesn't know) so that
someone can get use of her $200. Anyway, just keep
passing it on.
Cream together: 2 cups butter
2 cups sugar
2 cups brown sugar
Add: 4 eggs
2 tsp. vanilla
Mis together in
separate bowl: 4 cups flour
5 cups oatmeal (put small
amounts of oatmeal in blender until it turns to
powder. Measure out 5 cups of oatmeal and only
"powderize" that, NOT 5 cups "powderized" oatmeal)
1 tsp salt
2 tsp baking powder
2 tsp baking soda
Mix: All of the above
Add: 24 oz. bag of chocolate chips and
1 finely grated 8 oz Hershey bar (plain)
Add: 3 cups chopped nuts (any kind)
Bake on greased cookie sheet (make golf ball sized balls) and
bake about two inches apart. Bake at 350 degrees for 8 - 10
minutes. DO NOT OVERBAKE. Makes 112.
From: ucdavis!lll-lcc!hplabs!parcvax! (John R. Bane)
Subject: Re: free cookie foundation?
Hi! I "stole" your very expensive cookie recipe off the net. If you
want to send me your SnailMail address, I'll be glad to send you a
dollar (I would like to suggest this to the net, but I think there is
some netiquette rule against asking for money - or is that only money
for oneself?) to help defray the cost (it's not much, but if EVERYone
who took the recipe sent you a dollar, it would help).
Here also is another cookie recipe which I'm very fond of.
Makes 6-8 dozen
Bake at 375 degrees for ~10 min.
Cream together:
1 cup shortening (I use Weight Watcher's Reduced Calorie Margarine!)
1/4 cup peanut butter (I recommend the non-sugared kind)
1/2 cup sugar
1/2 cup brown sugar
2 eggs
1 teaspoon vanilla
1/2 cup flour
1 teaspoon soda
1/2 teaspoon salt
2 cups rolled oats (I use the 5-min variety)
1-2 cups chocolate chips (I use 2 cups semi-sweet - ummmm!)
1 cup nuts (I use pecan pieces - don't get them crushed, or the extra
oil will make greasy cookies)
1 cup shredded or flaked coconut
(The nuts were listed as optional and I added the coconut myself, but
I really love them there! You could also add things like m&m's, or
raisins (I don't care for raisins in cookies, but you might). I've
always wanted to try banana chips.)
Mix well. Drop by teaspoonfuls on greased cookie sheet (I use pam).
Bake at 375 degrees for approx. 10 min.
My aunt found this recipe in an Amish book called something like
"Eating Well When The Whole World Is Starving," and although I thought
a cookie recipe was a bit odd for a book like that, they are about the
healthiest a cookie is ever likely to get.
They are also very easy to make (no blending, sifting, rolling, etc.)
and extremely delicious. I get rave reviews and recipe requests whenever
I make them.
- rene
Chocolate Chip Cookies - Glamorous, crunchy, rich with chocolate bits & nuts.
Also known as "Toll House" Cookies ... from Kenneth and Ruth Wakefield's
charming New England Toll House on the outskirts of Whitman, Massachusetts.
These cookies were first introduced to American homemakers in 1939 through
our series of radio talks on "Famous Foods From Famous Eating Places."
Mix Thoroughly :
2/3 cup soft shortening ( part butter )
1/2 cup granulated sugar
1/2 cup brown sugar ( packed )
1 egg
1 tsp vanilla
Sift together and stir in :
1-1/2 cups sifted flour (*)
1/2 tsp soda
1/2 tsp salt
Stir in :
1/2 cup cut-up nuts
6 oz package of semi-sweet chocolate pieces ( about 1-1/4 cups )
(*) for a softer, more rounded cookie, use 1-3/4 cups sifted flour.
Drop rounded teaspoonfuls about 2" apart on ungreased baking sheet. Bake until
delicately browned ... cookies should still be soft. Cool slightly before you
remove them from the baking sheet.
Temperature: 375 F. ( modern oven )
Time: bake 8 - 10 minutes
Amount: 4 - 5 dozen 2" cookies
Personal comments :
I find it tastes better with a mixture of shortening and butter, as they say.
You don't need << all >> of that sugar, and it can be whatever color you want.
The nuts are optional. Feel free to play with the recipe. I put oatmeal in it,
reducing flour accordingly, and sometimes cinnamon.
I also find it useful to grease the cookie sheets.
I think I'm going to go bake some now ...
-- richard
......@@ -25,6 +25,36 @@ to operating system names (i.e. sunos4.1) or architecture names (i.e.
hppa1.1). If you leave out the version number, the `configure' script
will 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
......@@ -36,7 +66,21 @@ Alliant (fx80-alliant-bsd):
Alliant FX/2800 (i860-alliant-bsd)
Known to work with 18.58 and OS version 2.2, compiler version 1.3.
Known to work with 19.26 and OS version 2.2, compiler version 1.3.
Alpha (DEC) running OSF/1 (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
For 4.0 revision 564, and 4.0A and 4.0B, Emacs 20 seems to work
with no special configuration options.
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).
Altos 3068 (m68k-altos-sysv)
......@@ -55,55 +99,48 @@ Amdahl UTS (580-amdahl-sysv)
even worth trying to use it. Success was obtained with the
uts native C compiler on uts version 5.2.5.
Apollo running Domain (m68k-apollo-bsd)
Apollo running X Windows (m68k-apollo-bsd)
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.
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.
In `lib-src/Makefile', don't expect emacsclient and emacsserver to
compile. You might want to remove them from your makefile.
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.
Supposedly something in dired.c runs into a compiler bug.
Paraphrasing the statement should avoid the problem. I have not yet
received word as to the exact statement this is.
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.
The Apollo has a bizarre operating system which does not permit
Emacs to be dumped with preloaded pure Lisp code. Therefore, each
time you start Emacs on this system, the standard Lisp code is loaded
into it. Expect it to take a long time. You can prevent loading of
the standard Lisp code by specifying the -nl switch. It must
come at the beginning of the command line; only the -t and -batch
switches may come before it.
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.
There is one remaining problem on the Apollo. You must replace
the CPP line in src/Makefile with "CPP = /usr/lib/cpp".
The C preprocessor lives there rather than in /lib/cpp because the
Aegis OS uses the /lib directory as the repository for shared libraries.
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.
Here is a design for a method of dumping and reloading the relevant
necessary impure areas of Emacs.
On dumping, you need to dump only the array `pure' plus the
locations that contain values of forwarded Lisp variables or that are
protected for garbage collection. The former can be found by a
garbage- collection-like technique, and the latter are in the
staticprolist vector (see alloc.c for both things).
Reloading would work in an Emacs that has just been started; except
when a switch is specified to inhibit this, it would read the dump
file and set all the appropriate locations. The data loaded must be
relocated, but that's not hard. Those locations that are of type
Lisp_Object can be found by a technique like garbage-collection, and
those of them that point to storage can be relocated. The other data
read from the file will not need to be relocated.
Check out the file 'lisp/x-apollo.el'. To use it, add
The switch to inhibit loading the data base would be used when it
is time to dump a new data base.
(load "x-apollo")
This would take a few seconds, which is much faster than loading
the Lisp code of Emacs from scratch.
to your .emacs file. It provides useful default Apollo function key
AT&T 3b2, 3b5, 3b15, 3b20 (we32k-att-sysv)
......@@ -123,6 +160,11 @@ AT&T 3b2, 3b5, 3b15, 3b20 (we32k-att-sysv)
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
......@@ -134,7 +176,22 @@ AT&T 7300 or 3b1 (m68k-att-sysv)
support them, so you can remove the #define SHORTNAMES in that
Bull sps7 (m68k-bull-sysv)
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
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.
......@@ -161,7 +218,7 @@ Clipper (clipper-???)
Convex (c1-convex-bsd, c2-convex-bsd, c32-convex-bsd, c34-convex-bsd,
18.53 supposedly to work.
Support updated and residual bugs fixed in 19.26.
Cubix QBx/386 (i386-cubix-sysv)
......@@ -173,9 +230,31 @@ 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)
Version 19 works under Ultrix.
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.
......@@ -189,13 +268,26 @@ DECstation (mips-dec-ultrix or mips-dec-osf)
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 sys1147 with SVR3V5). Changes merged in 19.1.
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
Motorola Delta 187 (m88k-motorola-sysv or m88k-motorola-m88kbcs)
Motorola Delta 187 (m88k-motorola-sysv,
m88k-motorola-sysvr4, or
Machine support added in version 19.
HAVE_X_MENU does not work due to lack of insque.
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)
......@@ -225,6 +317,10 @@ Encore machine (ns16k-encore-bsd)
A kernel bug in some system versions causes input characters to be lost
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
......@@ -251,22 +347,52 @@ Gould NP1 (np1-gould-bsd)
Version 19 supposedly works.
Harris Night Hawk (m68k-harris-cxux or m88k-harris-cxux)
This port was added in 19.23. The configuration actually tested was
a Night Hawk 4800 running CX/UX 7.0.
If you have GCC ported and want to build with it, you probably need to
change things (like compiler switches) defined in the s/cxux.h file.
If you have X11R6 installed in /usr/lib, configure will fail to find
it and may find X11R5 instead. To work around this problem, use
--x-libraries=/usr/lib when you run configure.
With CX/UX 7.0 and later releases, you need to build after setting the
SDE_TARGET environment variable to COFF (a port using ELF and shared
libraries has not yet been done).
Harris Power PC (powerpc-harris-powerunix)
Patches have been merged in 19.31.
Honeywell XPS100 (xps100-honeywell-sysv)
Config file added in version 19.
HP 9000 series 200 or 300 (m68k-hp-bsd or m68k-hp-hpux7.)
Hewlett-Packard 9000 series 200 or 300 (m68k-hp-bsd or m68k-hp-hpux
or m68k-hp-netbsd)
Version 19 works under BSD.
These machines are 68000-series CPUs running HP-UX
These machines are 68000-series CPUs running HP/UX
(a derivative of sysV with some BSD features) or BSD 4.3 ported by Utah.
The operating system suffix determines which system Emacs is built for.
Series 200 HPUX runs Emacs only if it has the "HP-UX upgrade".
Series 200 HPUX runs Emacs only if it has the "HP/UX upgrade".
Version 19 works under BSD. The 19.26 pretest was reported
to work on HPUX 9. 19.31 works on HPUX 10.01, but there are
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
/usr/contrib/mitX11R5/lib, the problem does not happen.
If you are running HP-UX release 8.0 or later, you need the optional
"C/ANSI C" software in order to build Emacs (older releases of HP-UX
If you are running HP/UX release 8.0 or later, you need the optional
"C/ANSI C" software in order to build Emacs (older releases of HP/UX
do not require any special software). If the file "/etc/filesets/C"
exists on your machine, you have this software, otherwise you do not.
......@@ -281,14 +407,14 @@ HP 9000 series 200 or 300 (m68k-hp-bsd or m68k-hp-hpux7.)
processor and a 5.+ kernel has the new compiler.
Define C_SWITCH_MACHINE to be +X to make a version of Emacs that
runs on both 68010 and 68020 based hp-ux's.
runs on both 68010 and 68020 based HP/UX's.
Define HPUX_68010 if you are using the new assembler, for
a system that has a 68010 without a 68881. This is to say,
a s200 (upgraded) or s310.
Define the symbol HPUX_NET if you have the optional network features
that include the `netunam' system call. This is refered to as
that include the `netunam' system call. This is referred to as
Network Services (NS/9000) in HP literature.
HP 9000 series 500: not supported.
......@@ -297,14 +423,71 @@ HP 9000 series 500: not supported.
which relocates data in memory during execution of a program,
and support for it would be difficult to implement.
HP 9000 series 800 (Spectrum) (hppa1.0-hp-hpux)
HP 9000 series 700 or 800 (Spectrum) (hppa1.0-hp-hpux or hppa1.1-hp-hpux
or ...hpux9shr, or ...-nextstep)
Use hppa1.1 for the 700 series and hppa1.0 for the 800
series machines. (Emacs may not actually care which one you use.)
These files support HP's Precision Architecture machines
running HP-UX. It has been moderately tested on the Series
Support for NextSTEP was added in 19.31.
If you are running HP-UX release 8.0 or later, you need the optional
"C/ANSI C" software in order to build Emacs (older releases of HP-UX
Emacs 20 may work on HPUX 10. You need patch PHSS_6202 to install
the Xaw and Xmu libraries. On HPUX 10.20 you may need to compile with GCC;
when Emacs was compiled with HP's C compiler, HP92453-01 A.10.32.03,
the subprocess features failed to work.
19.26 is believed to work on HPUX 9 provided you compile with GCC.
As of version 19.16, Emacs was reported to build (using GCC) and run
on HP 9000/700 series machines running HP/UX versions 8.07 and 9.01.
The HP compiler is known to fail on some versions if you use +O3,
but it may work with lower optimization levels.
Use hppa1.1-hp-hpux9shr to use shared libraries on HPUX version 9.
You may need to create the X libraries libXaw.a and libXmu.a from
the MIT X distribute, and you may need to edit src/Makefile's
definition of LIBXT to look like this:
LIBXT= $(LIBW) -lXmu -lXt $(LIBXTR6) -lXext
Some people report trouble using the GNU memory allocator under
HP/UX version 9. The problems often manifest as lots of ^@'s in the
We are told that these problems go away if you obtain the latest
patches for the HP/UX C compiler. James J Dempsey
<> says that this set of versions works for him:
HP92453-01 A.09.28 HP C Compiler
HP92453-01 A.09.28 HP C Compiler
HP-UX SLLIC/OPTIMIZER HP-UX.09.00.23 02/18/93
Ucode Code Generator - HP-UX. (patch) 2/18/93
For 700 series machines, the HP-UX patch needed is known as
PHSS_2653. (Perhaps for 800 series machines as well; we don't
know.) If you are on the Internet, you should be able to obtain
this patch by using telnet to access the machine and logging in as "hpslreg" and following
the instructions there. Or you may be able to use this
web site:
HP Patch Server:
HP Support Line:
Please do not ask FSF for further support on this. If you have any
trouble obtaining the patch, contact HP Software Support.
If your buffer fills up with nulls (^@) at some point, it could well
be that problem. That problem does not happen when people use GCC
to compile Emacs. On the other hand, the HP compiler version 9.34
was reported to work for the 19.26 pretest. 9.65 was also reported to work.
If you turn on the DSUSP character (delayed suspend),
Emacs 19.26 does not know how to turn it off on HPUX.
You need to turn it off manually.
If you are running HP/UX release 8.0 or later, you need the optional
"C/ANSI C" software in order to build Emacs (older releases of HP/UX
do not require any special software). If the file "/etc/filesets/C"
exists on your machine, you have this software, otherwise you do not.
......@@ -321,6 +504,19 @@ High Level Hardware Orion 1/05 (clipper-highlevel-bsd)
C compiler has a bug; it loops compiling eval.c.
Compile it by hand without optimization.
HITACHI SR2001/SR2201 series (hppa1.1-hitachi-hiuxmpp)
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').
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.
IBM PS/2 (i386-ibm-aix1.1 or i386-ibm-aix1.2)
Changes merged in version 19. You may need to copy
......@@ -329,18 +525,38 @@ IBM PS/2 (i386-ibm-aix1.1 or i386-ibm-aix1.2)
i386-ibm-aix1.1 may not work with certain new X window managers, and
may be suboptimal.
IBM RS/6000 (rs6000-ibm-aix)
IBM RS/6000 (rs6000-ibm-aix*)
Emacs 19.26 is believed to work; its pretest was tested.
Changes merged in version 19. Currently the configuration
does not actually depend on the version of AIX.
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.
Compiling with -O using the IBM compiler has been known
to make Emacs work incorrectly.
to make Emacs work incorrectly. It's reported that on
AIX 3.2.5 with an IBM compiler earlier than,
cc -O fails for some files. You need to install any
PTF containing APAR #IX42810 to bring the compiler to
the level to allow optimized compiles.
There are reports that IBM compiler versions earlier than
fail even without -O. However, another report said that compiler
version did work, on AIX 3.2.4, with Emacs 19.31.
As of 19.11, if you strip the Emacs executable, it ceases to work.
If you are using AIX 3.2.3, you may get a core dump when loading
ange-ftp. You may be able to fix the problem by defining LIBS_TERMCAP
as -ltermcap -lcurses. Please tell us if this fails to work.
If anyone can fix the above problems, or confirm that they don't happen
with certain versions of various programs, we would appreciate it.
IBM RT/PC (romp-ibm-bsd or romp-ibm-aix)
18.52 worked on both operating systems.
Use romp-ibm-bsd for the 4.2-like system and romp-ibm-aix for AIX.
19.22 is reported to work under bsd. We don't know about AIX.
On BSD, if you have trouble, try compiling with a different compiler.
......@@ -366,21 +582,78 @@ Integrated Solutions `Optimum V' (m68k-isi-bsd4.2 or -bsd4.3)
in a system header file, which confuses Emacs (which thinks that UMAX
indicates the Umax operating system).
Intel 386 (i386-unknown-isc, i386-unknown-esix, i386-unknown-xenix,
i386-intsys-sysv, i386-unknown-sysv5.2.2, i386-unknown-sysv5.3,
and i386-unknown-bsd4.2)
18.58 should support a wide variety of operating systems.
Make sure to use i386-unknown-isc2.2 for Interactive 386/ix version
2.2 or later.
Use i386-unknown-esix for Esix.
Intel 386 (i386-*-isc, i386-*-esix, i386-*-bsdi2,
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-*-sco3.2v4, i386-*-bsd386, i386-*-386bsd,
i386-*-msdos, i386-*-windowsnt.
i386... can be replaced with i486... or i586...)
In the above configurations, * means that the manufacturer's name
you specify does not matter, and you can use any name you like
(but it should not contain any dashes or stars).
When using the ISC configurations, be sure to specify the isc
version number - for example, if you're running ISC 3.0, use
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.