Updated the files. Added some notes concerning our experience with SuSE Linux 10.0.

MAINTENANCE

@@ -107,7 +107,7 @@ installation, the file alberta/src/Common/gltools.c is included in the ALBERTA
 libraries. The user can specify the path of an already installed
 gltools-package as a "configure" option, see INSTALL.
 
-IV) Checking into CVS directory tree
+IV) Checking into Subversion directory tree
 ====================================
 
 Step 0)
@@ -160,7 +160,7 @@ Step 1)
   package with the directory structure described right at the
   beginning of this file.
 
-    svn checkout svn+ssh://pizza.math.uni-augsburg.de/homes/andere/alberta/ALBERTA_SVN/trunk albertadist
+    svn checkout svn+ssh://marbella.math.uni-augsburg.de/homes/andere/alberta/ALBERTA_SVN/trunk albertadist
 
   also checks out administration directories in each module. This
   is ok, since Makefiles produced by "configure" have a fixed set of
@@ -183,6 +183,12 @@ Step 2)
   "generate-alberta-automakefiles.sh" in the top directory.
 
 Step 3)
+  Rebuild the Makefile.am's for the ALBERTA libraries, this is done by
+  running the shell-script
+
+  ./generate-alberta-automakefiles.sh
+
+Step 4)
   Make sure you have a recent version of GNU "automake", "autoconf" and
   "libtool" and run "autoreconf" in the "albertadist" directory. We
   recommend running "autoreconf --install --force" to be certain that 
@@ -194,20 +200,6 @@ Step 3)
 
   where you have to replace foobar by the proper name of the program.
 
-  Keep this in mind when upgrading to new versions of libtool and
-  autoconf. In particular, when upgrading one should check whether
-  those two hacks are still needed.
-
-Step 4)
-  Rebuild the Makefile.am's for the ALBERTA libraries, this is done by
-  running the shell-script
-
-  ./generate-alberta-automakefiles.sh
-
-  Then run remake all Makefile.in's (and all other auto-generated files):
-
-  autoreconf
-
 Step 5)
   Reconfigure ALBERTA with the additional switch
   "--enable-maintainer-mode":
@@ -215,7 +207,7 @@ Step 5)
   ./configure BLABLABLA --enable-maintainer-mode
 
 Step 6)
-  Do "[g]make dist" at the top level.  This creates alberta-1.3.tar.gz
+  Do "[g]make dist" at the top level.  This creates alberta-?.?.tar.gz
   in which all CVS-directories, ~-files, and other unnecessary
   components are stripped. To be a bit more precise:
 
@@ -247,6 +239,8 @@ Choosing not to use libtool would require many changes, the first
 would be to change all "LTLIBRARIES" to "LIBRARIES" in all
 "Makefile.am"s.
 
+Here we have some cases of operating systems (produced as output of the 
+script "config.guess"):
 1) mips-sgi-irix6.5:
   a) The -lgl and -lGL libraries are required.
   b) The GNU Fortran compiler g77 distributed by SGI produced n32-style
@@ -256,9 +250,12 @@ would be to change all "LTLIBRARIES" to "LIBRARIES" in all
     ii) Using the system compilers cc and f77.
 
 2) i686-suse-linux:
-  a) We used MesaGL and a BLAS lib included in our distribution. If MesaGL
-     is not found, "configure" will also try "GL". The alberta_util lib needed 
-     -lg2c to process FORTRAN code properly.
+  a) SuSE 9.2: We used MesaGL and a BLAS lib included in our
+     distribution. If MesaGL is not found, "configure" will also try "GL". The 
+     alberta_util lib needed "-lg2c" to process FORTRAN code properly.
+
+  b) SuSE 10.0: Trouble with the FORTRAN compiler. Try running
+     F77=gfortran ../configure
 
 3) sparc-sun-SunOS:
   a) For the xdr-Routines, the library -lnsl seemed necessary.

README

@@ -456,6 +456,16 @@ example 1.)
 V. Some platform dependent notes and examples
 =============================================
 
+0) Compilation under SuSE Linux:
+--------------------------------
+a) SuSE 9.2: We used MesaGL and a BLAS lib included in our
+   distribution. If MesaGL is not found, "configure" will also try "GL". The 
+   alberta_util lib needed "-lg2c" to process FORTRAN code properly.
+
+b) SuSE 10.0: More trouble with the FORTRAN compiler. Try running
+   F77=gfortran ../configure
+
+
 1) Intel's  "math core library" libmkl:
 ------------------------------------
 Make sure to also link with libguide, this can be achieved by the