hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph H Castain (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-8099) Change to nodemanager build now requires 32-bit libraries
Date Wed, 22 Feb 2012 01:20:48 GMT
Change to nodemanager build now requires 32-bit libraries
---------------------------------------------------------

                 Key: HADOOP-8099
                 URL: https://issues.apache.org/jira/browse/HADOOP-8099
             Project: Hadoop Common
          Issue Type: Bug
    Affects Versions: 0.23.0
         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

        

Mime
View raw message