Gerco Ballintijn gerco-at-cwi.nl |Subclipse mailing list| 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
>
>
Looks like I was missing the link to libexpat.so.1 as well as libdb-4.2.
Thanks for the two tips. Would it perhaps be possible for Subclipse to
print out some info to the error log in situations like this? I wasn't
familiar with Eclipse's plugin structure, so I was at a loss for how to
find out what I needed. My first attempt was to look at the log, but
there was nothing helpful there. Works for me now, but it's the sort of
thing that might point others in the right direction. Thanks!
Received on Wed Jul 21 18:47:10 2004