Details
Description
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.
Attachments
Attachments
Issue Links
- is duplicated by
-
MAPREDUCE-3922 Fix the potential problem compiling 32 bit binaries on a x86_64 host.
- Resolved