You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2015/05/28 00:37:17 UTC
[jira] [Commented] (ACCUMULO-3662) Verify correct looking JAVA_HOME
in build_native_library.sh
[ https://issues.apache.org/jira/browse/ACCUMULO-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561873#comment-14561873 ]
Christopher Tubbs commented on ACCUMULO-3662:
---------------------------------------------
I think we can add a quick check to verify {{$JAVA_HOME/bin/javah}} exists in the Makefile, right? That should be sufficient to determine if the JAVA_HOME points to a JDK. After that, we can just assume the JNI headers are in the include directory. We could check for the JNI headers directly, but that may not be as platform-independent as checking for the existence of javah.
Do we need to do this check on Darwin also, or just Linux? I mean, can we assume Darwin has a JDK installed, or no?
> Verify correct looking JAVA_HOME in build_native_library.sh
> -----------------------------------------------------------
>
> Key: ACCUMULO-3662
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3662
> Project: Accumulo
> Issue Type: Improvement
> Components: scripts
> Reporter: Josh Elser
> Assignee: Christopher Tubbs
> Priority: Critical
> Labels: newbie, usability
> Fix For: 1.6.3, 1.8.0, 1.7.1
>
>
> JAVA_HOME needs to be set to a valid JDK to run {{build_native_library.sh}} successfully. Either it's extracted from the environment or it's set in accumulo-env.sh.
> Either way, when it isn't set (or set incorrectly), we should catch this, print a warning and exit the script to prevent the deluge 'JNI_EXPORT' related error messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)