[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151552#comment-17151552
 ] 

David Vujic commented on ZOOKEEPER-3879:
----------------------------------------

Thank you [~eolivelli] for explaning how to run the script! I managed to run it 
on my Linux machine (Mac OS X didn't work). A lot of tests ran (a couple of 
them failed though). But it doesn't look like the C Client was built? What I 
would like to do is being able to run the *autoreconf* command, as described 
[in the 
docs|[https://github.com/apache/zookeeper/blob/master/zookeeper-client/zookeeper-client-c/README]].
 The output from that is used when building a Node.js native addon, based on 
the C Client source code.

On Linux, after *mvn clean install*, I also tried navigating to the 
zookeeper-client-c folder to run the autoreconf command. But got the same 
errors as described in the first post here.

> C Client: how to build?
> -----------------------
>
>                 Key: ZOOKEEPER-3879
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3879
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: c client
>    Affects Versions: 3.6.1
>            Reporter: David Vujic
>            Priority: Major
>
> I have tried to follow the [installation 
> guide|https://github.com/apache/zookeeper/tree/master/zookeeper-client/zookeeper-client-c],
>  but cannot understand how to make the *autoreconf* step to work. It is 
> failing at the AM_PATH_CPPUNIT missing. Have tried the suggestions in the 
> guide, but without success. 
> The OS I have used are Mac OS X and Elementary OS. Also, went trying using 
> CentOS in a docker container, but cannot figure out how to add all 
> requirements (autoconf missing etc).
> Previous builds of the Zookeeper C Client (3.5.x) have worked fine though, I 
> guess something has changed?
> For the development of node-zookeeper, this is a blocker.
> Do you have any suggestions how to solve this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to