hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3922) Document solution for potential problem compiling 32 bit binaries on a x86_64 host.
Date Mon, 27 Feb 2012 19:06:46 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217397#comment-13217397

Allen Wittenauer commented on MAPREDUCE-3922:

The real fix is to revert the hardcode, not document a specific fix for a specific OS packaging
system.  While I know there are lots of places in the native code where this is done, it is
NEVER safe to hard-code CFLAG and LDFLAG settings without testing the validity of those values.

> Document solution for potential problem compiling 32 bit binaries on a x86_64 host.
> -----------------------------------------------------------------------------------
>                 Key: MAPREDUCE-3922
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3922
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Eugene Koontz
>            Assignee: Eugene Koontz
>            Priority: Minor
>              Labels: bigtop, build, doc, mrv2
>         Attachments: MAPREDUCE-3922.patch
> MAPREDUCE-3880 specifies that {{-m32}} be passed to gcc to ensure that a 32-bit binary
is built. On my Amazon Linux with a x86_64 architecture, I could not build the native container-executor
because the configure script exited with an error when trying to use gcc (version 4.4.5) with
this flag.
> Adds a comment to {{hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/pom.xml}}
regarding package requirement for glibc-devel.i686 or glibc-devel.i386 package on yum-based
(RHEL, Centos, Amazon) Linux distributions.

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


View raw message