lilypond-1.1.44

diff --git a/Documentation/topdocs/INSTALL.yo b/Documentation/topdocs/INSTALL.yo
index 2faf016ea83c71182c1da70932f25f3b05606919..91a2f829721d32c58eade30c3b8df327333843d4 100644 (file)
--- a/Documentation/topdocs/INSTALL.yo
+++ b/Documentation/topdocs/INSTALL.yo
@@ -9,6 +9,15 @@ file(buildscripts/set-lily.sh) script.  It sets some environment
 variables and symlinks, which comes in handly when you have to compile 
 LilyPond more often.  
 
+sect(OBTAINING)
+
+You can get the latest version of LilyPond at
+lurl(ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/).  Refer to the links
+document for mirror sites.
+
+em(If you upgrade by patching do remember to rerun autoconf after
+applying the patch).
+
 sect(PREREQUISITES)
 
 For compilation you need:
@@ -51,7 +60,7 @@ find various files.  The recommended way of doing so is adjusting the
 environment variables in the start-up scripts of your shell.  An
 example is given here for the Bourne shell:
 verb(export MFINPUTS="/usr/local/share/lilypond/mf:"
-export TEXINPUTS="/usr/local/share/lilypond/tex:"
+export TEXINPUTS="/usr/local/share/lilypond/tex:/usr/local/share/lilypond/ps:"
 )
 The empty path component
 represents TeX() and MetaFont's default search paths.  Scripts with
@@ -74,7 +83,8 @@ or any mirror of this site.
 it()Bison (version 1.25 or newer).
 Check out lurl(ftp://ftp.gnu.org)
 or any mirror of this site.
-it() GUILE 1.3 (no, GUILE 1.2 won't work),     check out lurl(http://www.gnu.org/programs/guile.html)
+it() GUILE 1.3 (no, GUILE 1.2 won't work),
+check out lurl(http://www.gnu.org/programs/guile.html).
 
 
 it()Python (version 1.5 or newer).  Check out
@@ -134,7 +144,7 @@ to install GNU LilyPond, simply type:
 verb(
        gunzip -c lilypond-x.y.z | tar xf -
        cd lilypond-x.y.z
-       configure               # fill in your standard prefix with --prefix
+       ./configure             # fill in your standard prefix with --prefix
        make
        make install
 )
@@ -158,7 +168,7 @@ adjust your environment variables to your taste:
 
 verb(
        export CPPFLAGS="-I /home/me/my_include -DWEIRD_FOOBAR" 
-       configure
+       ./configure
 )
 
 code(CPPFLAGS) are the preprocessor flags. 
@@ -168,7 +178,7 @@ bf(--help). If you are not root, you will probably have to make it
 with a different bf(--prefix) option.  Our favourite location is
 
 verb(
-       configure --prefix=$HOME/usr
+       ./configure --prefix=$HOME/usr
 )
 
 In this case, you will have to set up MFINPUTS, and TEXINPUTS accordingly.
@@ -216,7 +226,7 @@ want to build with and   without profiling.  Then I'd use the
 following for the normal build, 
 
 verb(
-      configure --prefix=~ --disable-optimise --enable-checking
+      ./configure --prefix=~ --disable-optimise --enable-checking
       make
       make install
      )
@@ -224,7 +234,7 @@ verb(
 and for the profiling version, I specify a different configuration.
 
 verb(
-      configure --prefix=~ --enable-profiling --enable-config=optprof --enable-optimise --disable-checking
+      ./configure --prefix=~ --enable-profiling --enable-config=optprof --enable-optimise --disable-checking
       make config=optprof
       make config=optprof install
 )