[
https://issues.apache.org/jira/browse/MESOS-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378262#comment-14378262
]
James Peach commented on MESOS-2537:
------------------------------------
Configure options:
{code}
configure \
--enable-silent-rules \
--disable-optimize \
--enable-debug \
--prefix=/opt/mesos
{code}
Unpatched results:
{code}
CXX: g++
CXXFLAGS: -g -O2 -Wno-unused-local-typedefs -std=c++11
CPPFLAGS: -I/usr/include/subversion-1 -I/usr/include/apr-1
-I/usr/include/apr-1.0
LDFLAGS:
LIBS: -lsasl2 -lsvn_delta-1 -lsvn_subr-1 -lapr-1 -lcurl -lz -lrt
{code}
Patched results:
{code}
CXX: g++
CXXFLAGS: -g -O0 -Wno-unused-local-typedefs -std=c++11
CPPFLAGS: -I/usr/include/subversion-1 -I/usr/include/apr-1
-I/usr/include/apr-1.0
LDFLAGS:
LIBS: -lsasl2 -lsvn_delta-1 -lsvn_subr-1 -lapr-1 -lcurl -lz
-lrt
{code}
> 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
> Reporter: James Peach
> Priority: Minor
>
> 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.4#6332)
