You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2013/04/10 20:02:15 UTC

[jira] [Updated] (HADOOP-9468) JVM path embedded in fuse binaries

     [ https://issues.apache.org/jira/browse/HADOOP-9468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Mackrory updated HADOOP-9468:
----------------------------------

    Status: Patch Available  (was: Open)
    
> JVM path embedded in fuse binaries
> ----------------------------------
>
>                 Key: HADOOP-9468
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9468
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>         Attachments: 0001-HADOOP-9468.-Not-embedding-JVM-library-paths-in-FUSE.patch
>
>
> When the FUSE binaries are built, the paths to libraries in the JVMs is embedded in the RPATH so that they can be found at run-time. From an Apache Bigtop perspective, this is not sufficient because the software may be run on a machine configured very differently from the one on which they were built - so a wrapper sets LD_LIBRARY_PATH according to JAVA_HOME. I recently saw an issue where the original JVM path existed, causing LD_LIBRARY_PATH to be ignored in favor of the RPATH, but it was not the JVM intended for running Hadoop (not JAVA_HOME), and this caused problems.
> I'm told that setting LD_LIBRARY_PATH is standard practice before using the fuse program anyway, and if that's the case, I think removing the RPATH from the binaries is a good idea.

--
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