[
https://issues.apache.org/jira/browse/MAPREDUCE-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213183#comment-13213183
]
Hitesh Shah commented on MAPREDUCE-3890:
----------------------------------------
@Ralph, this was from MAPREDUCE-3880 to get the RC build unblocked but yes, the
right fix would be to use an env flag that could be handled in the configure
step.
> Change to nodemanager build now requires 32-bit libraries
> ---------------------------------------------------------
>
> Key: MAPREDUCE-3890
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3890
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.23.1
> Environment: Centos 6, x86_64
> Reporter: Ralph H Castain
>
> Sometime during the last week, someone committed a change to:
> hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/pom.xml
> that inserted a -m32 in:
> <configureEnvironment>
> <property>
> <name>CFLAGS</name>
> <value>-DHADOOP_CONF_DIR=${container-executor.conf.dir}
> -m32</value>
> This breaks the build on 64-bit systems that do not have 32-bit libraries
> installed. The change was actually not required as 64-bit support for JNI and
> JVMs is readily available and installed by default on many 64-bit systems.
> Removing the flag results in a completed and functional build.
> If mandating 32-bit builds is desired, then a better solution would be to
> provide a configure flag such as -DHADOOP_32bit_MODE, perhaps with a
> corresponding flag for 64-bit. Regardless, locking the system to 32-bit
> builds seems a tad extreme.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
