vm/current should build by itself ... it's stuff like AWT that sometimes
requires outside help.
--John
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Bryce McKinlay
> Sent: Thursday, December 07, 2000 4:49 PM
> To: Brian Jones
> Cc: GNU Classpath
> Subject: Re: DataInputStream changes...
>
>
> Brian Jones wrote:
>
> > > 4. (and this is the problem that I'm stuck on) jikes doesn't seem to
> > > believe that files in java/lang and vm/reference/java/lang are
> > > actually in the same package. ie: when its building java/lang and
> > > looks for Runtime.java, it doesn't "find" it in
> > > vm/reference/java/lang even though vm/reference is on the classpath.
> > > What I can't understand is why japhar's implementation of these
> > > files wouldn't also suffer from this problem - or does the japhar
> > > build symlink them or copy its files into a single directory? or
> > > what?
> >
> > Interesting. The configure script symbolically links vm/reference to
> > vm/current. The lib/Makefile.am should be appropriate at that point
> > to compile things.
>
> I wonder, does this work for you because you still have someone elses
> classes.zip available at this point? So the vm/current files are actually
> building against classes from the other vendors java.lang?
>
> regards
>
> [ bryce ]
>
>
>
> _______________________________________________
> Classpath mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/classpath
>
_______________________________________________
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath
