Chris Toshok <[EMAIL PROTECTED]> writes:
> "Aaron M. Renn" wrote:
>
> > I synced up with CVS and now have Japhar working with the old Classpath
> > 0.00 release. Looks like John's patch did the job. I did have a
> > problem with core dumps that required me to add /usr/local/japhar/lib
> > to LD_LIBRARY_PATH manually.
>
> strange... what were the core dumps? /usr/local/japhar/lib is only checked
> after the directories in LD_LIBRARY_PATH are checked, so if you have older
> native libs your path that could be the problem.
>
> > Also, I still don't seem to have all of
> > my libraries loaded correctly because I'm getting some runtime link errors.
> > Are the library files still supposed to be called libjaphar_whatever.so?
>
> they can be either libjaphar_%s.so or lib%s.so. japhar tries to load the
> libjaphar_%s.so library first, and if it can't find it it tries lib%s.so.
>
I may have changed a couple of lib names today without changing the
load in the .java file to match. My mistake. I'll fix it tomorrow.
Brian
--
Brian Jones <[EMAIL PROTECTED]>
