From 0196b30aebe9cad125799d97b86146d3d2dcab17 Mon Sep 17 00:00:00 2001 From: Jim Blandy Date: Fri, 2 Aug 1996 21:21:11 +0000 Subject: [PATCH] *** empty log message *** --- ChangeLog | 5 +++ INSTALL | 112 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ README | 10 +++++ 3 files changed, 127 insertions(+) create mode 100644 INSTALL create mode 100644 README diff --git a/ChangeLog b/ChangeLog index 9a758e615..3acfccd64 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,10 @@ Thu Aug 1 02:31:53 1996 Jim Blandy + * doc/Makefile.in: Added pattern targets for creating DVI and + PostScript files. + (%.ps, %.dvi, %.txt): New targets. + (DVIPS, TEXI2DVI): New variables. + * GUILE-VERSION: Updated to 1.0b3. Rehashed distribution system, in preparation for nightly diff --git a/INSTALL b/INSTALL new file mode 100644 index 000000000..02295045a --- /dev/null +++ b/INSTALL @@ -0,0 +1,112 @@ +Building libguile.a and guile + + To build Guile on unix, there are two basic steps: + + 1. Configure the package by running the configure script. + 2. Build the package by running make. + +Generic instructions for configuring and compiling GNU distributions +are included below. Here is an illustration of commands that might be +used to build Guile. The voluminous output of the commands is not shown. + + % tar xvf guile-1.0b1 # unpack the sources + % mkdir guile-1.0b1-build # create the build dir + % ../guile-1.0b0/configure --prefix=$INST_ROOT + % make install + +The installed results are an executable called "guile1.0", a library +called "libguile1.0", and some header files. + +If you run "guile", you'll get a "guile> " prompt to which you can +type Scheme forms. + + + + Generic Instructions for Building Auto-Configured Packages + ========================================================== + + +To compile this package: + +1. Configure the package for your system. In the directory that this +file is in, type `./configure'. If you're using `csh' on an old +version of System V, you might need to type `sh configure' instead to +prevent `csh' from trying to execute `configure' itself. + +The `configure' shell script attempts to guess correct values for +various system-dependent variables used during compilation, and +creates the Makefile(s) (one in each subdirectory of the source +directory). In some packages it creates a C header file containing +system-dependent definitions. It also creates a file `config.status' +that you can run in the future to recreate the current configuration. +Running `configure' takes a minute or two. + +To compile the package in a different directory from the one +containing the source code, you must use GNU make. `cd' to the +directory where you want the object files and executables to go and +run `configure' with the option `--srcdir=DIR', where DIR is the +directory that contains the source code. Using this option is +actually unnecessary if the source code is in the parent directory of +the one in which you are compiling; `configure' automatically checks +for the source code in `..' if it does not find it in the current +directory. + +By default, `make install' will install the package's files in +/usr/local/bin, /usr/local/lib, /usr/local/man, etc. You can specify +an installation prefix other than /usr/local by giving `configure' the +option `--prefix=PATH'. Alternately, you can do so by changing the +`prefix' variable in the Makefile that `configure' creates (the +Makefile in the top-level directory, if the package contains +subdirectories). + +You can specify separate installation prefixes for machine-specific +files and machine-independent files. If you give `configure' the +option `--exec_prefix=PATH', the package will use PATH as the prefix +for installing programs and libraries. Normally, all files are +installed using the same prefix. + +`configure' ignores any other arguments that you give it. + +If your system requires unusual options for compilation or linking +that `configure' doesn't know about, you can give `configure' initial +values for some variables by setting them in the environment. In +Bourne-compatible shells, you can do that on the command line like +this: + CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure + +The `make' variables that you might want to override with environment +variables when running `configure' are: + +(For these variables, any value given in the environment overrides the +value that `configure' would choose:) +CC C compiler program. + Default is `cc', or `gcc' if `gcc' is in your PATH. +INSTALL Program to use to install files. + Default is `install' if you have it, `cp' otherwise. +INCLUDEDIR Directory for `configure' to search for include files. + Default is /usr/include. + +(For these variables, any value given in the environment is added to +the value that `configure' chooses:) +DEFS Configuration options, in the form '-Dfoo -Dbar ...' +LIBS Libraries to link with, in the form '-lfoo -lbar ...' + +If you need to do unusual things to compile the package, we encourage +you to teach `configure' how to do them and mail the diffs to the +address given in the README so we can include them in the next +release. + +2. Type `make' to compile the package. + +3. Type `make install' to install programs, data files, and +documentation. + +4. You can remove the program binaries and object files from the +source directory by typing `make clean'. To also remove the +Makefile(s), the header file containing system-dependent definitions +(if the package uses one), and `config.status' (all the files that +`configure' created), type `make distclean'. + +The file `configure.in' is used as a template to create `configure' by +a program called `autoconf'. You will only need it if you want to +regenerate `configure' using a newer version of `autoconf'. diff --git a/README b/README new file mode 100644 index 000000000..5fbcff936 --- /dev/null +++ b/README @@ -0,0 +1,10 @@ +This is beta release 1.0b3 of Guile, the GNU extension language library. + +Guile is a portable, embaddable Scheme implementation written in C. +Guile provides a machine independent execution platform that can be +linked in as a library when building extensible programs. + +Guile is derived from SCM, by Aubrey Jaffer and others. Tom Lord +librarified SCM, yeilding Guile. He wrote Guile's operating system, +Ice-9, connected Guile to Tcl/Tk and the `rx' regular expression +matcher, and took care of a lot of miscellany.