> From: C. Brian Jones [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Jones
>
> "John Keiser" <[EMAIL PROTECTED]> writes:
>
> > The only thing I had to do that wasn't in the docs (that I
> could find) is
> > "ln -s /usr/local/japhar/lib/classpath/lib_*.so libjaphar_*.so"
> (roughly).
> > That was a slight pain to figure out, and if I hadn't done
> something like
> > that before. If you need to do that, I have a Perl script
> attached. Run it
> > in <japhar_install_dir>/lib/classpath.
>
> This is what I was missing, thanks. Time to find bugs. Should
> probably fix up the install to make those symlinks when installing to
> japhar since they appear to be required.
>
Yes, that would be good ... if you can do that, I will find some time
(probably not until this weekend) and write up a simple guide to downloading
and installing Japhar+Classpath from scratch.
> The vm integration doc should probably cover the looping dependency
> issue and possible solutions, you think?
>
Yeah, that's true ... I'll add a note. I've been thinking about it, and
probably the best rule of thumb to use is to make sure the VM interface
depends on as few static variables and methods from everything else.
I have a question, I think it was you who messed around with Kaffe ... do
you think the fixes I just made need to be applied to the Kaffe stuff (i.e.
was the Kaffe stuff copied from the reference implementation)?
--John
