You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Charles Reiss (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/19 18:54:36 UTC

[jira] [Resolved] (MESOS-136) Zookeeper's CPPUnit dependency doesn't have access to required macro on Red-Hat

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

Charles Reiss resolved MESOS-136.
---------------------------------

    Resolution: Fixed

Now that we build zookeeper by unpacking the tarball, this issue shouldn't happen.
                
> Zookeeper's CPPUnit dependency doesn't have access to required macro on Red-Hat
> -------------------------------------------------------------------------------
>
>                 Key: MESOS-136
>                 URL: https://issues.apache.org/jira/browse/MESOS-136
>             Project: Mesos
>          Issue Type: Bug
>          Components: build
>         Environment: Red-Hat (amazon's AMI)
>            Reporter: Matthew Rathbone
>            Priority: Minor
>              Labels: build-failure, zookeeper
>
> Firstly the readme should probably state that to build with zookeeper you need to have CPPUNIT installed
> on Red hat:
> sudo yum install cppunit-devel
> However, the zookeeper cofigure script assumes access to the macro:
> AM_PATH_CPPUNIT(<version>)
> All this does is check to see if the currently installed cppunit version is >= whatever is required, in this case 1.10.2. On red-hat, for whatever reason, the script does not have access to this macro.
> I fixed this issue by commenting out the offending line in the zookeeper configure script, and everything built fine.  I think the manual inclusion of /usr/share/aclocal/ccpunit.m4 will also fix the problem (this is where the macro is defined), although I haven't tested this assertion.
> This seems related to: https://issues.apache.org/jira/browse/ZOOKEEPER-316

--
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