*** empty log message ***

[bpt/guile.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index 8f2cb3e..e0e0b33 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -29,6 +29,9 @@ HP/UX: GCC 2.7.2 (and maybe other versions) have trouble creating
     suggest you configure Guile to use the system's C compiler:
        CC=cc ./configure
 
+NetBSD: Perry Metzger says, "Guile will build under NetBSD only using
+    gmake -- the native make will not work.  (gmake is in our package
+    system, so this will not be a problem when we packagize 1.3.)"
 
 What You Get ==============================================================
 
@@ -70,20 +73,20 @@ libqt.a, which you will need to link into your programs after
 libguile.a.  That is, you should pass the switches -lguile -qt to your
 linker.
 
-Coop threads are not yet thoroughly tested; once they are, they will
-be enabled by default.  The interaction with blocking I/O is pretty ad
-hoc at the moment.  In our experience, bugs in the thread support do
-not affect you if you don't actually use threads.
-
-At the moment, threads are known not to work with the NetBSD 1.2
-assembler.
+Cooperative threads are not yet thoroughly tested; once they are, they
+will be enabled by default.  The interaction with blocking I/O is
+pretty ad hoc at the moment.  In our experience, bugs in the thread
+support do not affect you if you don't actually use threads.
 
 --enable-dynamic-linking --- Build a Guile executable and library
 providing Scheme functions which can load a shared library and
 initialize it, perhaps thereby adding new functions to Guile.  This
-feature is not yet thoroughly tested; once it is, it will be enabled
-by default.  This option has no effect on systems that do not support
-shared libraries.
+feature is enabled by default; you only need to use this option (as
+`--enable-dynamic-linking=no') if you want to build a Guile which does
+not support dynamic linking.
+
+This option has no effect on systems that do not support shared
+libraries.
 
 --disable-shared --- Do not build shared libraries.  Normally, Guile
 will build shared libraries if your system supports them.  Guile
@@ -99,24 +102,16 @@ separate build directory, you'll need to include the build directory
 in the path as well.
 
 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:
+called `/home/jimb/guile-snap' (so the full name of this INSTALL file
+would be `/home/jimb/guile-snap/INSTALL').  Then you might say, if
+you're using Bash or any other Bourne shell variant,
 
   export GUILE_LOAD_PATH=/home/jimb/guile-snap
 
-if you're using Bash or any other Bourne shell variant, or
+or if you're using CSH or one of its variants:
 
   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 GUILE_LOAD_PATH as
-well.  For example, if you built in a subdirectory of the source tree
-called `pentium', you might say:
-
-  export GUILE_LOAD_PATH=/home/jimb/guile-snap:/home/jimb/guile-snap/pentium
-
 
 Building a Statically Linked Guile ========================================