2002-02-09 Eric Blake <ebb9@email.byu.edu>

	* INSTALL: Update instructions for using jikes 1.15b.
	* HACKING: Ditto.
	* ChangeLog: Clean up some whitespace.

1 files changed, 30 insertions, 19 deletions

diff --git a/INSTALL b/INSTALL
index 74db79ec9..1cce09f12 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,4 +1,4 @@
-Installing GNU Classpath - Last updated: Feb. 07, 2002
+Installing GNU Classpath - Last updated: Feb. 09, 2002
 
 First, this is a development release only! Unless you are interested in
 active development and debugging, or just like running random alpha code,
@@ -15,20 +15,27 @@ Suggested Software
         - GNU automake 1.5
         - GNU libtool 1.4.2
 
-	For building the Java bytecode (.class files)
+	For building the Java bytecode (.class files), one of these
+	compilers are required.  You can select which compiler using
+	--with-jikes, --with-gcj or --with-kjc as argument to
+	configure; the present default is gcj.  The javac compiler
+	included in any of Sun's JDKs will not work, as it will not
+	compile java.lang.Object.
 
-        - IBM jikes 1.13 (newer versions up to 1.15 appear to be broken)
-          or GCJ 3.0.2+.  The kjc compiler is supported with configure 
-          but we have been unable to successfully compiled with it.
-	  Jikes is currently the default compiler.  You can select the
-	  compiler using --with-jikes, --with-gcj or --with-kjc as argument
-	  to configure.
-
-	  Note that GCC 3.1 (from CVS) is currently broken, if you do
-	  want to use it look at the status of the following bug:
+        - GCJ 3.0.2+ (part of the GNU GCC package).  Note that GCC
+	  3.1 (from CVS) is currently broken, if you do want to use it
+          look at the status of the following bug:
 	<http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&database=gcc&pr=4715>
-	  Applying the patch in that report to gcc/jva/parse.y does seem to
-	  solve/work around the problem.
+	  Applying the patch in that report to gcc/jva/parse.y does
+          seem to solve/work around the problem.
+        - IBM jikes 1.15b+.  You may have success with 1.13, but other
+          versions will fail.  Until jikes 1.16 is released, you will
+          have to use CVS access and build jikes 1.15b yourself:
+          cvs login :pserver:anoncvs@www-124.ibm.com:/usr/cvs/jikes
+            (password anoncvs)
+          cvs co -r v1-15b jikes          
+        - The kjc compiler is supported with configure but we have
+          been unable to successfully compile with it.
 
 	For building the JNI native libraries, the following are required.
 
@@ -83,12 +90,16 @@ found at <http://www.gnu.org/software/classpath/doc/orp.html>.
 ------------------------------------------------------------------
 Misc. Notes
 ------------------------------------------------------------------
-Use of Sun's compiler is deprecated and probably does not work.  At
-least three free compilers are supported: gcj, jikes, and kjc.
-
-Compilation is accomplished using a compiler's @file syntax.  For our part, 
-we avoid placing make style dependencies as rules upon the compilation 
-of a particular class file and leave this up to the Java compiler instead.
+Compilation is accomplished using a compiler's @file syntax.  For our
+part, we avoid placing make style dependencies as rules upon the
+compilation of a particular class file and leave this up to the Java
+compiler instead.
 
 The --enable-maintainer-mode option to configure currently does very 
 little and shouldn't be used by ordinary develoeprs or users anyway.
+
+On Windows machines, the native libraries do not currently build, but
+the Java bytecode library will.  Unfortunately, as gcj does not yet
+compile under cygwin or mingw32, and the mingw32 version of jikes
+cannot follow symbolic links, you must use a cygwin build of jikes to
+access this limited functionality.