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

["Kamil Domański (JIRA)" <ji...@apache.org>]

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

Kamil Domański updated MESOS-1776:
----------------------------------
    Comment: was deleted

(was: As it turns out, {{\-\-without-package}} cannot be disabled because it is a canonical style handled by autoconf itself and not by the script. I will instead make {{\-\-without-package}} behave just like {{\-\-with-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
>            Assignee: 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)