[
https://issues.apache.org/jira/browse/HADOOP-8737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443633#comment-13443633
]
Colin Patrick McCabe commented on HADOOP-8737:
----------------------------------------------
Hi Allen,
Thanks for letting me know you're having problems under OS X. Can you clarify
what the problem is?
Searching around brings up references to {{JAVA_HOME}} not being set on OS X.
However, the native build is already using {{JAVA_HOME}}. For example,
{{./hadoop-common-project/hadoop-common/pom.xml}} contains this text:
{code}
<configuration>
<javahPath>${env.JAVA_HOME}/bin/javah</javahPath>
<javahClassNames>
<javahClassName>org.apache.hadoop.io.compress.zlib.ZlibCompressor</javahClassName>
<javahClassName>org.apache.hadoop.io.compress.zlib.ZlibDecompressor</javahClassName>
{code}
> 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
> Attachments: HADOOP-8737.001.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
