You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "James Page (Commented) (JIRA)" <ji...@apache.org> on 2012/01/17 14:04:39 UTC
[jira] [Commented] (BIGTOP-305) hadtoop's "task-controller.c"
builds both 32 AND 64 bit versions in a 32bit environment
[ https://issues.apache.org/jira/browse/BIGTOP-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187638#comment-13187638 ]
James Page commented on BIGTOP-305:
-----------------------------------
A fix was proposed for this in https://issues.apache.org/jira/browse/MAPREDUCE-2178 but it was never committed as far as I can tell.
Fix was to drop use of AC_SYS_LARGEFILES for task-controller to avoid this issue.
> hadtoop's "task-controller.c" builds both 32 AND 64 bit versions in a 32bit environment
> ---------------------------------------------------------------------------------------
>
> Key: BIGTOP-305
> URL: https://issues.apache.org/jira/browse/BIGTOP-305
> Project: Bigtop
> Issue Type: Bug
> Components: Debian
> Affects Versions: 0.2.0
> Environment: ubuntu 10.10 32bit vm
> Reporter: Sid Askary
> Assignee: Roman Shaposhnik
> Priority: Minor
>
> Cannot build bigtop for 32bit environ. Get the following error msg:
> [exec] In file included from /home/<....>/bigtop/output/hadoop/hadoop-0.20.205.0/src/c++/task-controller/impl/task-controller.c:24:
> [exec] /usr/include/fts.h:41: error: #me/error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64"ation shows
> [exec] make[1]: *** [impl/task-controller.o] Error 1
> [exec] make[1]: Leaving directory `/home/<...>/bigtop/output/hadoop/hadoop-0.20.205.0/build/c++-build/Linux-i386-32/task-controller'
> Further investigation shows that both versions are in the directory:
> <...>/bigtop/build/hadoop/deb/hadoop-0.20.205.0/c++
> Linux-amd64-64 Linux-i386-32
> This seems to be a Hadoop bug for the "task-controller". Please verify and push up to Hadoop team...
--
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