On Fri, Aug 15, 2008 at 8:26 AM, Markus Schönhaber
<subclipse-users_at_list-post.ddt-consult.de> wrote:
> Jens Seidel schrieb:
>
>> I remember that on a 64 bit platform javahl was not found by default by
>> Subclipse in /usr/lib64/ which is one of the default linker paths on
>> this system (there was an entry in /etc/ld.so.conf). As far as I
>> remember it was explained on this list that java behaves differently
>> and doesn't follow ld's configuration.
>
> I'm not sure, but maybe the javahl libs are loaded by doing something
> like System#loadLibrary()/Runtime#getRuntim#loadLibrary() and these Java
> methods only look into the paths in java.library.path (Mark will know,
> if this really is true or not). And if java.library.path did't contain
> /usr/lib64 this directory would be left out when looking for the javahl
> libs.
I am definitely not an expert, but I've helped a lot of people and
gathered anecdotal experience from that.
In theory you should not need LD_LIBRARY_PATH, and my understanding is
that most Linux distributions now do not even set that variable and
discourage its use. However, the JVM automatically adds the contents
of that variable to java.library.path, so setting it can help. The
approach I now take is to use the eclipse.ini. I have recently
started an FAQ:
http://desktop-eclipse.open.collab.net/wiki/JavaHL
Tigris.org is going to be upgraded in about a month and when it does
we will have a Wiki and I will cut and paste this over to the
Subclipse project.
My understanding is that Java needs java.library.path in order to find
and load the JavaHL library. When that library loads, it loads
libraries according to the normal rules. From my experience, as long
as Java can load JavaHL, the library can typically load its
dependencies.
A problem I have been seeing a lot recently, and someone mentioned it
earlier, is that people will edit their eclipse.ini, but their Eclipse
launcher shortcut will have options like -vm or -vmargs on it. When
you do this, the launcher does not read the eclipse.ini file. So make
sure you move all command line options into the .ini file.
Finally, the 32/64-bit nature of JavaHL needs to match your JVM. If
the JVM is 64-bit, then JavaHL needs to be.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-08-15 15:23:39 CEST