Also, I should point out that lib/ doesn't compile yet anyway. We have
issues. This is the first time all of classpath has gotten together in a
standard build procedure. On that, be patient.
If you'd like to help fix compilation errors and get us on our way, then
that's great! Leave lib/ in there.
If you're just trying to get it running under Japhar using the new patch,
remove "lib" from the subdirs in Makefile.am and redo "aclocal; autoheader;
autoconf; automake; ./configure --with-japhar=...; make".
--John Keiser
> -----Original Message-----
> From: Moses DeJong [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 02, 1998 3:36 PM
> To: [EMAIL PROTECTED]
> Subject: I just tried to compile the CVS code (help)
>
>
> I just got the cvs tree and tried to compile it. Here is what went
> wrong.
>
>
> java -classpath /usr/local/java/lib/classes.zip sun.tools.javac.Main
> -classpath ../lib:/usr/local/java/lib/classes.zip -d ../lib
> ../java/lang/Cloneable.java
> Unable to initialize threads: cannot find class java/lang/Thread
>
> This is just so wrong. The configure script should NEVER use java
> on the sun.tools.javac.Main class. Why dont you just use this?
>
> javac -d ../lib ../java/lang/Cloneable.java
>
>
> It would work and you would not get into the horrible problems
> of finding the correct classes.zip to include in the -classpath
> argument (this is really ugly because different ports do it
> different ways). If you just use "javac" then you will not run
> into these issues. In addition other jvms will not call the
> compiler sun.tools.javac.Main. Could someone please fix this?
>
>
> Mo DeJong
> dejong at cs.umn.edu
>
>
