[ 
https://issues.apache.org/jira/browse/MAPREDUCE-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roman Shaposhnik updated MAPREDUCE-3890:
----------------------------------------

    Status: Patch Available  (was: Open)

Attaching a patch that makes it possible to build the container-executor binary 
that has the default system architecture. Just add -Dcontainer-executor.arch=" 
" to the build and you're done. This will unblock Bigtop packaging efforts and 
will let us use 0.23.1 as the basis of Hadoop RPM and DEBIAN packaging.

Feel free to modify to suit your needs. Or apply as is. The (unfortunate) 
default behavior of pretending that every workstation is fully configured with 
32bit environment is preserved.
                
> 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
>          Components: build, mrv2
>    Affects Versions: 0.23.1
>         Environment: Centos 6, x86_64
>            Reporter: Ralph H Castain
>            Assignee: Ralph H Castain
>             Fix For: 0.23.2
>
>         Attachments: MAPREDUCE-3890.patch.txt
>
>
> 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

        

Reply via email to