You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Timothy St. Clair (JIRA)" <ji...@apache.org> on 2014/09/12 16:10:33 UTC

[jira] [Comment Edited] (MESOS-1776) --without-PACKAGE will set incorrect dependency prefix

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

Timothy St. Clair edited comment on MESOS-1776 at 9/12/14 2:09 PM:
-------------------------------------------------------------------

This is a bug in the logic, but there are few dependencies that can be treated --without-package. 

Is the intent to build against system dependencies or disable functionality?



was (Author: tstclair):
This is a bug in the logic, but there are few dependencies that can be treated --without-package. 


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