When trying to launch an application I get a java.lang.UnsatisfiedLinkError: no <libname> in java.library.path

I've put export LD_LIBRARY_PATH= statements in the .bash_profile of the user I'm logged in as and in /etc/profile
but when I type 'echo $LD_LIBRARY_PATH' at the command line I get a blank line returned. The last line of the 'set' command output where the LD_LIBRARY_PATH output is reads:
_=<path to jar file I want to execute>
although I have only specified paths to directories not individual files in the LD_LIBRARY_PATH

When I execute the jar file from the command line with the -Djava.library.path= specified as an argument I get a different (but I think unrelated error) Can anyone shed some light on this?

I hope you have relogged in after you put this in the profile files.
They are read only on login.
If they still dont work export it from the command prompt like this:

export LD_LIBRARY_PATH=/xxx/yyy

and then echo it once to check.
This should work

--Ukesh Upendran

I've changed the /etc/profile and the user's and root's .bashrc to contain:
LD_LIBRARY_PATH=/usr/ofed/lib:<other colon-seperated entries here>

export LD_LIBRARY_PATH

and yes, I have been logging out and in again for the changes to take affect. For some reason, though, launching the jar file from command line doesn't give me this problem but executing the same command from a launcher on the desktop (I'm using RHEL 4) does.

You can make the library universally available with the ldconfig command. Log in as root and add the library to the /etc/ld.so.conf file. Then run the ldconfig command as root. See:

man ldconfig

----------------------
Steve Stites

A jar file cannot be run directly from a Desktop Entry.

Make a shell script with your java -jar command ..
Name the script, make it executable, cp the script to
/usr/local/bin/

Now you can call the script from a Desktop Entry with
exec=scriptname .
....