[ https://issues.apache.org/jira/browse/HADOOP-8806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455512#comment-13455512 ]
Colin Patrick McCabe commented on HADOOP-8806: ---------------------------------------------- bq. [rpath discussion] The problem is, we don't know at compile-time where libsnappy.so will be. Normally there's a "make install" step where rpaths get injected, but there is nothing like that for Hadoop. Sadly, I have encountered an issue that I think puts the kibosh on the "static libsnappy" idea-- you cannot link a .a into a .so. I don't know why I didn't think of that earlier. > libhadoop.so: search java.library.path when calling dlopen > ---------------------------------------------------------- > > Key: HADOOP-8806 > URL: https://issues.apache.org/jira/browse/HADOOP-8806 > Project: Hadoop Common > Issue Type: Improvement > Reporter: Colin Patrick McCabe > Priority: Minor > > libhadoop calls {{dlopen}} to load {{libsnappy.so}} and {{libz.so}}. These > libraries can be bundled in the {{$HADOOP_ROOT/lib/native}} directory. For > example, the {{-Dbundle.snappy}} build option copies {{libsnappy.so}} to this > directory. However, snappy can't be loaded from this directory unless > {{LD_LIBRARY_PATH}} is set to include this directory. > Should we also search {{java.library.path}} when loading these libraries? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira