Now I remember,
It was looking for libexpat.so.1 or libexpat.so.0, but some
distributions like my Gentoo number
the .so differently than what javahl expects.
So all you need to do is to create either a libexpat.so.1 link to
libexpat.so.0 or the other way around.
On Wed, 21 Jul 2004 09:41:49 +0200, Gerco Ballintijn <gerco@cwi.nl> wrote:
> ividqwr02@sneakemail.com wrote:
> >
> > Since then, I've poked around a bit, and I know of three separate Subclipse
> > installations into Eclipse 3 which are all unable to use the Javahl bindings.
> > All 3 are under linux, so I'm wondering if ANY linux user has javahl working.
> > If there are people with it working, what's wrong with all of the
> > installations I've found? This obviously isn't a one-off problem anymore.
> >
>
> A frequently occuring problem is that the shared libraries on which
> your libjavahl.so depends do not exits. So, go to the subclipse core
> directory (plugins/org.tigris.subversion.subclipse.core_*), and type
> the command:
>
> ldd libsvnjavahl.so
>
> This shows which actual shared libraries are used for which reference.
> When some libaries cannot be found (usually libdb-*.so or libexpat.so)
> those libaries first need to be installed.
>
> Hope this helps.
>
> Gerco.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
--
Alwyn Schoeman
Mid-life crisis in action
Received on Wed Jul 21 18:34:28 2004