[ 
https://issues.apache.org/jira/browse/HADOOP-8737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443837#comment-13443837
 ] 

Hudson commented on HADOOP-8737:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #2684 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2684/])
    HADOOP-8737. cmake: always use JAVA_HOME to find libjvm.so, jni.h, 
jni_md.h. Contributed by Colin Patrick McCabe (Revision 1378444)

     Result = FAILURE
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1378444
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/JNIFlags.cmake

                
> cmake: always use JAVA_HOME to find libjvm.so, jni.h, jni_md.h
> --------------------------------------------------------------
>
>                 Key: HADOOP-8737
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8737
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: native
>    Affects Versions: 2.2.0-alpha
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>             Fix For: 2.2.0-alpha
>
>         Attachments: HADOOP-8737.001.patch, HADOOP-8737.002.patch
>
>
> We should always use the {{libjvm.so}}, {{jni.h}}, and {{jni_md.h}} under 
> {{JAVA_HOME}}, rather than trying to look for them in system paths.  Since we 
> compile with Maven, we know that we'll have a valid {{JAVA_HOME}} at all 
> times.  There is no point digging in system paths, and it can lead to host 
> contamination if the user has multiple JVMs installed.

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

Reply via email to