Failed to load JavaHL library

Question

After updating Snow Lion, I started getting these errors in Flash Builder / Eclipse when trying to use SVN:

Failed to load JavaHL Library. These are the errors that were encountered: no libsvnjavahl-1 in java.library.path /opt/subversion/lib/libsvnjavahl-1.0.dylib: Library not loaded: /usr/lib/libpq.5.dylib Referenced from: /opt/subversion/lib/libsvnjavahl-1.0.dylib Reason: no suitable image found. Did find: /usr/lib/libpq.5.dylib: mach-o, but wrong architecture /usr/lib/libpq.5.dylib: mach-o, but wrong architecture no svnjavahl in java.library.path java.library.path = .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java 

Answer 1

If you don't need to use JavaHL, Subclipse also provides the SVN API library with pure Java - SVNKit (http://svnkit.com). Just install the client adapter and SVNKit library plugins from the Subclipse update site, and then select it in the Team> SVN settings.

Answer 2

Try the following:

• Choose Window → Preferences
• Expand Command → SVN
• In the SVN interface, install Client on SVNKit (Pure Java) SVNKit ....

Answer 3

In Kubuntu, my library path has changed due to installing a different version of Java. Here's the whole picture , but briefly:

 sudo apt-get install libsvn-java sudo find / -name libsvnjavahl-1.so 

The result of the last command might look like this:

/usr/lib/x86_64-linux-gnu/jni/libsvnjavahl-1.so

This gives you a way, so you can add the following to your eclipse.ini :

 -Djava.library.path=/usr/lib/x86_64-linux-gnu/jni/ 

Answer 4

Check out this blog . It has a lot of information. Also, if installing through brew do not miss this note:

You may need to bind Java bindings in the Java Extensions folder:

  $ sudo mkdir -p /Library/Java/Extensions $ sudo ln -s /usr/local/lib/libsvnjavahl-1.dylib /Library/Java/Extensions/libsvnjavahl-1.dylib 

Answer 5

I just installed Mountain Lion and had the same problem. I am using FLASHBuilder (32bit) and MountainLion is 64 bit, which means that MacPorts installs everything as 64-bit by default. The subheading version I'm using is 1.8. Since I already installed Subversion and JavaHLBindings, I just ran this command:

  sudo port upgrade --enforce-variants active +universal 

This caused the Mac ports to go through all the already installed ones and also installed the 32-bit version.

Then I restarted FlashBuilder and no longer detected JavaHL errors.

Answer 6

Perhaps you may need JavaHL or it depends on your OS. In addition to other offers, simply posting it here.

For other OSs, see this source: http://subclipse.tigris.org/wiki/JavaHL

Answer 7

maybe you can try this: change jdk version. And I solved this problem by changing jdk from 1.6.0_37 to 1.6.0.45. BR!

Answer 8

I tried every available solution and finally the problem for me:

 uninstall Native JavaHL 1.6 install everything under Subclipse from this site: 

http://subclipse.tigris.org/update_1.10.x >

Answer 9

For me, I started getting this problem when I upgraded to java 8 and then reverted back to java 7. Updated again to java 8 and the problem was resolved.

Answer 10

My understanding. Basically, the svn client works by default on Mac os. When installing in eclipse, we must map the svn plugin to the mac plugin and javaHL will not be missing. There is a lengthy upgrade process by installing xcode and then using homebrew or macports, which you can find after searching the web, but if you are in a hurry, just follow these steps.

1) on your Mac shell

$ svn --version

Write down the version, for example. 1.7.

2) open the link below

http://subclipse.tigris.org/wiki/JavaHL

check which version of the subtitle you need, corresponding to it. eg

Subtitle Version SVN / JavaHL Version 1.8.x 1.7.x

3) ok, take the url corresponding to 1.8.x from

http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA

and add in your eclipse => Install new software under the help

select everything you need, svn client or subclipse or mylyn etc., and it will ask you to restart STS / eclipse if you do. worked for me.

NOTE. If you already have several versions installed inside your eclipse, then it is best to remove all versions of client subclasses or svn from eclipse plugins and start with the new steps listed above.