You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Akira Kitada (Commented) (JIRA)" <ji...@apache.org> on 2011/12/11 06:59:40 UTC
[jira] [Commented] (ZOOKEEPER-705) Fails to Build due to unknown
opcode 'lock' in mt_adaptor.c
[ https://issues.apache.org/jira/browse/ZOOKEEPER-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167054#comment-13167054 ]
Akira Kitada commented on ZOOKEEPER-705:
----------------------------------------
__sync_fetch_and_add is a gcc built-in function.
I think it was added in somewhere in gcc 4.1.
> Fails to Build due to unknown opcode 'lock' in mt_adaptor.c
> -----------------------------------------------------------
>
> Key: ZOOKEEPER-705
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-705
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client
> Affects Versions: 3.2.2
> Reporter: Thomas Koch
> Assignee: Thomas Koch
> Priority: Minor
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-705.patch
>
>
> The Debian package of Zookeeper[1] fails to build on some architectures, see below. The issue is an unknown assembler opcode. The Bugs is reported in the debian bugtracker as #568618[2]. A patch is available. I've uploaded it here too for your convenience.
> [1] http://packages.qa.debian.org/z/zookeeper.html
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568618
> Buildd status overview:
> https://buildd.debian.org/status/package.php?p=zookeeper
> Some Failed Buildd Logs:
> Sparc: https://buildd.debian.org/fetch.cgi?pkg=zookeeper;ver=3.2.2%2Bdfsg3-2;arch=sparc;stamp=1265466795
> S390: https://buildd.debian.org/fetch.cgi?pkg=zookeeper;ver=3.2.2%2Bdfsg3-2;arch=s390;stamp=1265415637
> powerpc: https://buildd.debian.org/fetch.cgi?pkg=zookeeper;ver=3.2.2%2Bdfsg3-2;arch=powerpc;stamp=1266677031
> mipsel: https://buildd.debian.org/fetch.cgi?pkg=zookeeper&arch=mipsel&ver=3.2.2%2Bdfsg3-2&stamp=1268124320&file=log&as=raw
--
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