You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2015/10/29 22:04:27 UTC
[jira] [Assigned] (MESOS-3600) unable to build with non-default
protobuf
[ https://issues.apache.org/jira/browse/MESOS-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Peach reassigned MESOS-3600:
----------------------------------
Assignee: James Peach
> unable to build with non-default protobuf
> -----------------------------------------
>
> Key: MESOS-3600
> URL: https://issues.apache.org/jira/browse/MESOS-3600
> Project: Mesos
> Issue Type: Bug
> Components: build
> Reporter: James Peach
> Assignee: James Peach
>
> If I install a custom protobuf into {{/opt/protobuf}}, I should be able to pass {{--with-protobuf=/opt/protobuf}} to configure the build to use it.
> On OS X, this fails:
> {code}
> ...
> checking google/protobuf/message.h usability... yes
> checking google/protobuf/message.h presence... yes
> checking for google/protobuf/message.h... yes
> checking for _init in -lprotobuf... no
> configure: error: cannot find protobuf
> -------------------------------------------------------------------
> You have requested the use of a non-bundled protobuf but no suitable
> protobuf could be found.
> You may want specify the location of protobuf by providing a prefix
> path via --with-protobuf=DIR, or check that the path you provided is
> correct if youre already doing this.
> -------------------------------------------------------------------
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)