Commit 973f4886 authored by eg's avatar eg

Initial Hg commit

Erick Gallesio <>
This diff is collapsed.
This diff is collapsed.
Basic Installation
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
The file `' is used to create `configure' by a program
called `autoconf'. You only need `' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. 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.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Compiling For Multiple Architectures
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
Installation Names
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/' if it exists, then
`PREFIX/etc/' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
`configure' recognizes the following options to control how it
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
Print a summary of the options to `configure', and exit.
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.
# for STklos
# Author: Erick Gallesio []
# Creation date: 11-Apr-2000 10:30 (eg)
# Last file update: 3-Nov-2005 22:08 (eg)
SUBDIRS = @PCRE@ @GC@ @GMP@ src utils lib @GTKLOS@ @EXAMPLES@ \
extensions tests doc
(cd tests; $(MAKE) test)
svn commit
svn update
rm -rf /usr/tmp/$(VERSION_BETA)
svn export $(SVN_URL)/trunk /usr/tmp/$(VERSION_BETA)
svnclonedates `pwd` /usr/tmp/$(VERSION_BETA)
beta: prep-version
( cd /usr/tmp; tar cvfz $(VERSION_BETA).tar.gz $(VERSION_BETA) )
ls -ls /usr/tmp/$(VERSION_BETA).tar.gz
version: prep-version
-svn rm $(SVN_URL)/tags/$(VERSION_TAG) -m ''
svn copy . $(SVN_URL)/tags/$(VERSION_TAG) -m ''
rm -rf /usr/tmp/$(VERSION_TAG)
cp -a /usr/tmp/$(VERSION_BETA) /usr/tmp/$(VERSION_TAG)
( cd /usr/tmp; tar cvfz $(VERSION_TAG).tar.gz $(VERSION_TAG) )
ls -ls /usr/tmp/$(VERSION_TAG).tar.gz
# oldversion:
# svn commit
# svn update
# -svn rm $(SVN_URL)/tags/$(VERSION_TAG) -m ''
# svn copy . $(SVN_URL)/tags/$(VERSION_TAG) -m ''
# rm -rf /usr/tmp/$(VERSION_TAG)
# svn export $(SVN_URL)/tags/$(VERSION_TAG) /usr/tmp/$(VERSION_TAG)
# clonedates `pwd` /usr/tmp/$(VERSION_TAG)
# ( cd /usr/tmp; tar cvfz $(VERSION_TAG).tar.gz $(VERSION_TAG) )
# ls -ls /usr/tmp/$(VERSION_TAG).tar.gz
This diff is collapsed.
-*- outline -*-
| NEWS |
* version 0.71 (2005 11 03)
* Added virtual ports (ports defined by user functions)
* The reader accepts now #eof to denote the eend of file object
* Fix problems with SunOS support
* Fix problems with gcc4 compilation
* Hash tables are now compliant to SRFI-69 (Basic Hash Tables).
This implies some (compatible) changes in the hash-tables
function names.
* New primitives
o finite?
o infinite?
o unsetenv!
o file-size
* New implemented SRFIs
o SRFI-62 (S-expression comments)
o SRFI-69 (Basic Hash Tables)
o SRFI-70 (Numbers)
* Bug fixes
* version 0.70 (2005 05 27)
The main changes in this release are: a new back-trace system, a
conform call/cc/dynamic-wind implementation and some performance
* Added a way to have a back-trace when an error occurs
* call/cc has been completely implemented. Its interaction with
dynamic-wind is now conform to R5RS.
* Perfomance improvements
* Added some infrastructure for auto-testing a newly built system.
* New primitives
+ port-rewind
+ port-seek
+ current-loading-file
+ decode-float
+ read/ss
+ write/ss
+ repl
* Multiple EOF can be seen now on an input file to allow staged
* Added the configure options --with-provided-gc and
--with-provided-regexp to force the usage of our GC and PCRE
versions, even if there are some version already installed on
the system
* The boot file is now integrated in the VM instead of being read
from a file. This enhances the loading time of the interpreter
a bit.
* Describe shows more information for structures types and
* The object system takes now into account conditions and
conditions types
* Documentation updated
* Bug fixes
* version 0.61 (2005 04 05)
* Documentation updated
* Distribution uses now PCRE 5.0 for regexp
* Build process has changed
* Performance improvement thanks to VM and I/O optimizations
* Added a way to download and install STklos extensions
* Better error signaling on undefined variables when compiling files
* Minor enhancements:
o Some corrections in the reader
o Parameter objects SRFI-39 (Parameters objects) can be used
now in generalized set! SRFI-17 (Generalized set!)
o Reader can be case-sensitive now (the system can be
bootstraped using case sensitive read)
o ...
* New primitives
o eval-from-string
o require/provide
o read-chars
o read-chars!
o write-chars
o get-password
* Implementation of SRFI-60 (Integers as bits)
* Bug fixes
* version 0.60 (2004 11 29)
This version is mostly a correcting version which fixes a serious bug
on file loading introduced in release 0.59. Very minor changes since
previous release
* SRFIs can also have symbolic names
* Minor modifications to allow the compilation of Skribe with
STklos on Win32
* A bunch of functions on dates
* Implementation of SRFI-55 (Require-extension)
* Bug fixes
Supported SRFIs: 0, 1, 2, 4, 6, 7, 8, 9, 10, 11, 13, 14, 16, 22, 23,
26, 27, 28, 30, 31, 34, 35, 36, 38, 39, 48, 55.
* version 0.59 (2004 11 04)
* Documentation has been rewritten in Skribe
* Added Dominique Boucher LALR(1) parser generator.
Thanks to Dominique for allowing me to do so
* Added the future R6RS comment syntax #;
* New primitives
o read-from-string
o load-path
o load-verbose
o load-suffixes
o fork
o port-current-position
o port-closed?
* New implemented SRFIs
o SRFI-10 (Sharp Comma External Form)
* Bug fixes
Supported SRFIs: 0, 1, 2, 4, 6, 7, 8, 9, 10, 11, 13, 14, 16, 22, 23,
26, 27, 28, 30, 31, 34, 35, 36, 38, 39, 48.
* version 0.58
* Better Win32 port (was no more fully functional since 0.55)
* Added a way to configure the system with our version of GMP even
* if GMP is installed
* Added structure types
* Stack size can be changed when the VM is launched
* New port on Octane/SGI Irix (by Joshua Boyd) and Itanium
* Added the --interactive option for embedded VM
* Compiler can add line information to the generated code to ease debugging
* error locations are more accurate now
* New primitives
o winify-file-name (for Win32 only)
o sleep
* New implemented SRFIs
o SRFI-34 (Exception Handling for Programs)
o SRFI-35 (Conditions)
o SRFI-36 (I/O Conditions)
o SRFI-48 (Intermediate Format Strings)
* Bug fixes
Supported SRFIs: 0, 1, 2, 4, 6, 7, 8, 9, 11, 13, 14, 16, 22, 23, 26,
27, 28, 30, 31, 34, 35, 36, 38, 39, 48
* version 0.57
* Added support for non Finked Mac-OS X
* Added the Danny Dubé SIlex lexical analyser generator
to the distribution. Thanks to Danny for allowing me to do so
* New primitives
o fork
o register-exit-function!
o html->string
o uri-parse
o chmod
* New implemented SRFIs
o SRFI-16 (Syntax for procedures of variable arity)
o SRFI-26 (Notation for Specializing Parameters without Currying)
* Bug corrections
Supported SRFIs: 0, 1, 2, 4, 6, 7, 8, 9, 11, 13, 14, 16, 22, 23, 26,
27, 28, 30, 31, 38, 39
* version 0.56
* The reader recognizes now the DSSL keywords #!rest,
#!optional and #!key
* New implemented SRFIs: 27 (random), 38 (external
representation of shared structures) and 39 (parameter
* New parameter: REAL-PRECISION allow to change the precision
used when displaying a real number
* Modified primitives: GENSYM, PARSE-ARGUMENTS