You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Bannier (JIRA)" <ji...@apache.org> on 2017/02/27 09:12:45 UTC

[jira] [Commented] (MESOS-2537) AC_ARG_ENABLED checks are broken

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

Benjamin Bannier commented on MESOS-2537:
-----------------------------------------

[~karya]: Could this be backported to all currently supported releases (just updated the _Affected versions_ field)? Currently, support tools like e.g., {{support/tag.sh}} pass {{--disable-optimize}} which is still broken there. Together with the fix for MESOS-6606 this causes the support scripts to be broken in these versions.

> AC_ARG_ENABLED checks are broken
> --------------------------------
>
>                 Key: MESOS-2537
>                 URL: https://issues.apache.org/jira/browse/MESOS-2537
>             Project: Mesos
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.0.3, 1.1.1, 1.1.2
>            Reporter: James Peach
>            Assignee: James Peach
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> In a number of places, the Mesos configure script passes "$foo=yes" to the 2nd argument of {{AC_ARG_ENABLED}}. However, the 2nd argument is invoked when the option is provided in any form, not just when the {{\--enable-foo}} form is used. One result of this is that {{\--disable-optimize}} doesn't work.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)