mirror/guile
mirror/guile
1
Fork 0
mirror of https://git.savannah.gnu.org/git/guile.git synced 2025-06-09 21:40:33 +02:00
Code Activity

Refer to "GUILE_LOAD_PATH", instead of "SCHEME_LOAD_PATH".

Browse source
This commit is contained in:
Jim Blandy 1997-10-25 06:34:53 +00:00
parent 2e3685828a
commit cf591c72fe
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
INSTALL
View file

@ -93,7 +93,7 @@ always builds static libraries.
Using Guile Without Installing It =========================================
If you want to run Guile without installing it, set the environment
variable `SCHEME_LOAD_PATH' to a colon-separated list of directories,
variable `GUILE_LOAD_PATH' to a colon-separated list of directories,
including the directory containing this INSTALL file. If you used a
separate build directory, you'll need to include the build directory
in the path as well.
@ -102,20 +102,20 @@ For example, suppose the Guile distribution unpacked into a directory
called `/home/jimb/guile-snap' (so the full name of this file would be
`/home/jimb/guile-snap/INSTALL'). Then you might say:
export SCHEME_LOAD_PATH=/home/jimb/guile-snap
export GUILE_LOAD_PATH=/home/jimb/guile-snap
if you're using Bash or any other Bourne shell variant, or
setenv SCHEME_LOAD_PATH /home/jimb/guile-snap
setenv GUILE_LOAD_PATH /home/jimb/guile-snap
if you're using CSH or one of its variants.
If you built Guile in a separate directory from the source tree, then
you'll need to include your build directory in the SCHEME_LOAD_PATH as
you'll need to include your build directory in the GUILE_LOAD_PATH as
well. For example, if you built in a subdirectory of the source tree
called `pentium', you might say:
export SCHEME_LOAD_PATH=/home/jimb/guile-snap:/home/jimb/guile-snap/pentium
export GUILE_LOAD_PATH=/home/jimb/guile-snap:/home/jimb/guile-snap/pentium
Building a Statically Linked Guile ========================================