[
https://issues.apache.org/jira/browse/MESOS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Reiss resolved MESOS-137.
---------------------------------
Resolution: Fixed
I think this is fixed -- since we don't build zookeeper with
AC_CONFIG_SUBDIRS() anymore that the differing libtool versions won't be a
problem.
> When building, the version of libtool that get's created in the
> third_parth/zookeeper directory is the wrong version
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MESOS-137
> URL: https://issues.apache.org/jira/browse/MESOS-137
> Project: Mesos
> Issue Type: Bug
> Components: build
> Environment: Red Hat (Amazon AMI)
> Reporter: Matthew Rathbone
> Priority: Minor
> Labels: build-failure, zookeeper
>
> The libtool in the root mesos directory is version: libtool (GNU libtool)
> 2.2.10
> The version that gets created in the zookeeper directory is a different
> version. This causes building zookeeper to fail (as headers have already been
> created using the new version, or something like that).
> The solution is to replace third_parth/zookeeper/libtool with ./libtool when
> you see the error and run configure/make again (not sure at what point this
> occurs).
--
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
