commit 58c190f279f73402264dfe35a02e98fa6bd1c207
parent ebc9d1856f5298b3cac0b0053541d4e1a0720741
Author: tgoodwin <tgoodwin>
Date: Wed, 15 Jul 1998 14:12:53 +0000
remove comments about yacc, and change comments about old C compilers
Diffstat:
| M | INSTALL | | | 49 | ++++++++++++++++++------------------------------- |
1 file changed, 18 insertions(+), 31 deletions(-)
diff --git a/INSTALL b/INSTALL
@@ -1,9 +1,5 @@
COMPILING
-rc was written in portable ANSI C. If you don't have an ANSI compiler
-like gcc or something close (e.g., sgi's cc) read further down on
-how to convert rc's source to old C.
-
rc uses GNU autoconf and automake. The following commands are all you
need to configure, build, test, and install rc.
@@ -15,6 +11,8 @@ need to configure, build, test, and install rc.
This will build rc in the source directory (see below for details on how
to build rc in a different directory).
+BUILD AND CONFIGURATION OPTIONS
+
There are lots of options you can give to configure to modify rc's
behaviour. You can also select a command line history library to
link against---see the README file for details of where to find these
@@ -30,13 +28,12 @@ descending order of usefulness.
--with-editline
- This option tells rc to use the editline package (see the README .
- This is essentially a lightweight version of GNU readline, providing
- EMACS style command line editing and history. If the editline library
- is not installed in a standard place, you can tell configure where to
- find it by setting the environment variable LIBS. For example, the
- maintainer builds rc by copying libedit.a into the rc build directory
- and then running this configure command.
+ This option tells rc to use the editline package (see the README file
+ for details) to provide EMACS style command line editing and history.
+ If the editline library is not installed in a standard place, you can
+ tell configure where to find it by setting the environment variable
+ LIBS. For example, the maintainer builds rc by copying libedit.a into
+ the rc build directory and then running this configure command.
LIBS=-L. sh ../rc-1.5b3/configure --with-editline
@@ -51,7 +48,7 @@ descending order of usefulness.
LIBS=-L/usr/gnu/lib sh configure --with-readline
- --enable-history
+ --with-history
Use this option if you want to build and install the programs that
support a crude history mechanism.
@@ -120,10 +117,11 @@ and if you have either of those you probably don't want to bother with
dying or discarding the variables. This option disables the default
behaviour. You are unlikely to want this option on any Unix system.
-After you've built rc, you may wish to run it through a test script
-to see that everything is ok. Type `make trip' for this. This will
-produce some output, and end with "trip is complete". If the trip ends
-with "trip took a wrong turn..." please contact the maintainer.
+After you've built rc, I recommend that you run it through a test script
+to gain some confidence that all is working well. Type `make trip' to
+do this. This will produce some output, and should end with "trip is
+complete". If the trip instead ends with "trip took a wrong turn..."
+please contact the maintainer.
BUILDING IN ANOTHER DIRECTORY
@@ -133,20 +131,9 @@ are building rc for multiple architectures. All you need do is specify
the path to the configure script in the first step. Suitable `make's
include GNU, and SunOS, but not Irix, nor UnixWare.
-YACC
-
-The yacc that Sun ships with SunOS 4.1.1 calls malloc() to allocate
-space for the state stack, and requires a call to YYACCEPT or YYABORT to
-free this memory. This means that if rc takes an interrupt while parsing
-a command (say, if ^C is typed), yacc will leak away this memory. The
-solution is to use a yacc which statically allocates this array, such
-as the yacc in the BSD distribution. Berkeley yacc-generated y.tab.c
-and y.tab.h are shipped with rc in case you cannot get hold of Berkeley
-yacc.
-
OLD C
-If you need to convert rc's source into K&R C, you need to run the
-source through a filter called "unproto", posted in comp.sources.misc.
-A sample "cpp" shell script that I used to run unproto under SunOS is
-supplied with rc.
+rc needs an ISO C (89) compiler, or at least one that has a reasonable
+understanding of function prototypes, `<stdarg.h>', `void', and
+`volatile'. If you really need to compile rc with an ancient C
+compiler, please contact the maintainer.
