[
https://issues.apache.org/jira/browse/BIGTOP-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated BIGTOP-504:
---------------------------------
Attachment: BIGTOP-504.1.patch
Moved the `find` command into a new script called bigtop-detect-javalibs
(similar to bigtop-detect-javahome - which means the invocation will be further
simplified if and when we resolve BIGTOP-463).
I've also made this a bit more flexible so this can also serve for other
components that may needed it. Components list the libraries they need to link
against dynamically in JAVA_NATIVE_LIBS (in this case just libjvm.so), and the
required paths are returned in JAVA_NATIVE_PATH - which can be prepended to
LD_LIBRARY_PATH.
> provide a functionality for detecting libjvm.so in bigtop-utils
> ---------------------------------------------------------------
>
> Key: BIGTOP-504
> URL: https://issues.apache.org/jira/browse/BIGTOP-504
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Sean Mackrory
> Fix For: 0.6.0
>
> Attachments: BIGTOP-504.1.patch
>
>
> Currently, for hdfs fuse we have code lile this in the launcher script:
> {noformat}
> if [ "\${LD_LIBRARY_PATH}" = "" ]; then
> export LD_LIBRARY_PATH=/usr/lib
> for f in \`find \${JAVA_HOME}/jre/lib -name client -prune -o -name libjvm.so
> -exec dirname {} \;\`; do
> export LD_LIBRARY_PATH=\$f:\${LD_LIBRARY_PATH}
> done
> fi
> {noformat}
> It would be nice to provide this as a general purpose detection code in
> bigtop-utils.
--
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
