This isn’t a totally unreasonable question, but there’s no good answer, so for posterity, I’ll make an attempt at explaining why you got stuck, and why it won’t work. java.library.path isn’t guaranteed to be set from an environment variable at all. You can specify what you want it to be with -Djava.library.path=. More than likely, … Read more
On Linux, use colon : as separator (as you will do with the classpath option) as in: -Djava.library.path=/opt/hdf-java/build/bin:/opt/opencv-2.4.10/build/lib
Its default value depends on the operating system: On Windows, it maps to PATH On Linux, it maps to LD_LIBRARY_PATH On OS X, it maps to DYLD_LIBRARY_PATH
Add the containing directory to LD_LIBRARY_PATH before launching the application export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/some/pathOfContainingDirectory Use java -XshowSettings:properties to show the java.library.path (and others) value.
Had forgotten this issue… I was actually asking with Eclipse, sorry for not stating that originally. And the answer seems to be too simple (at least with 3.5; probably with older versions also): Java run configuration’s Arguments : VM arguments: -Djava.library.path=”${workspace_loc:project}\lib;${env_var:PATH}” Must not forget the quotation marks, otherwise there are problems with spaces in PATH.
I assume you’re running Hadoop on 64bit CentOS. The reason you saw that warning is the native Hadoop library $HADOOP_HOME/lib/native/libhadoop.so.1.0.0 was actually compiled on 32 bit. Anyway, it’s just a warning, and won’t impact Hadoop’s functionalities. Here is the way if you do want to eliminate this warning, download the source code of Hadoop and … Read more