Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4C87A10105 for ; Tue, 19 May 2015 16:33:01 +0000 (UTC) Received: (qmail 16380 invoked by uid 500); 19 May 2015 16:33:01 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 16330 invoked by uid 500); 19 May 2015 16:33:01 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 16316 invoked by uid 99); 19 May 2015 16:33:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2015 16:33:00 +0000 Date: Tue, 19 May 2015 16:33:00 +0000 (UTC) From: "Colin Patrick McCabe (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-11987) JNI build should use default cmake FindJNI.cmake MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-11987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550726#comment-14550726 ] Colin Patrick McCabe commented on HADOOP-11987: ----------------------------------------------- I understand that it would be cleaner to use the system-provided FindJNI.cmake. However, JNIFlags.cmake reflects a lot of fixes that people have contributed over the years. For example, there are hacks to detect soft-float ARM rather than hard-float ARM. It also supports generating 32-bit binaries when the JVM is 32-bit, even if the architecture is 64-bit. I do not think we can remove it without causing regressions for a significant number of users. > JNI build should use default cmake FindJNI.cmake > ------------------------------------------------ > > Key: HADOOP-11987 > URL: https://issues.apache.org/jira/browse/HADOOP-11987 > Project: Hadoop Common > Issue Type: Sub-task > Components: native > Affects Versions: 2.7.0 > Environment: All > Reporter: Alan Burlison > Assignee: Alan Burlison > Priority: Minor > > From http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201505.mbox/%3C55568DAC.1040303%40oracle.com%3E > ---------- > Why does hadoop-common-project/hadoop-common/src/CMakeLists.txt use JNIFlags.cmake in the same directory to set things up for JNI > compilation rather than FindJNI.cmake, which comes as a standard cmake > module? The checks in JNIFlags.cmake make several assumptions that I > believe are only correct on Linux whereas I'd expect FindJNI.cmake to be > more platform-independent. > ---------- > Just checked the repo of cmake and it turns out that FindJNI.cmake is > available even before cmake 2.4. I think it makes sense to file a bug > to replace it to the standard cmake module. Can you please file a jira > for this? > ---------- > This also applies to hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-nativetask/src/JNIFlags.cmake -- This message was sent by Atlassian JIRA (v6.3.4#6332)