[
https://issues.apache.org/jira/browse/MESOS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131720#comment-14131720
]
Kamil Domański commented on MESOS-1776:
---------------------------------------
With current logic *--disable-bundled* makes it impossible to enable some
select bundled packages but not the others. For example, I might want to use my
system's boost, protobuf, leveldb while having to use bundled gmock, zookeper,
etc.
Even with your interpretation, *--without-package* is handled in a faulty way.
I can indeed workaround this by specifying --with-package=*/usr* for each
package I want to use from system.
If you think the current state should be preserved, then please close this as
"Won't Fix".
> --without-PACKAGE will set incorrect dependency prefix
> ------------------------------------------------------
>
> Key: MESOS-1776
> URL: https://issues.apache.org/jira/browse/MESOS-1776
> Project: Mesos
> Issue Type: Bug
> Components: build
> Affects Versions: 0.20.0
> Reporter: Kamil Domański
> Labels: build
>
> When disabling a particular bundled dependency with *--without-PACKAGE*, the
> build scripts of both Mesos and libprocess will set a corresponding variable
> to "no". This is later treated as prefix under which to search for the
> package.
> For example, with *--without-protobuf*, the script will search for *protoc*
> under *no/bin* and obviously fail. I would propose to get rid of these
> prefixes entirely and instead search in default locations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
