[
https://issues.apache.org/jira/browse/MESOS-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531119#comment-14531119
]
Cody Maloney commented on MESOS-2690:
-------------------------------------
So {{\-\-enable\-optimize}}, inside the script we add the {{\-O2}} as a
user-shortcut. {{\-\-enable-optimize}} we provide as a user shortcut, and if
people touch CXXFLAGS themselves, it doesn't do anything (Didn't use to
anyways, with https://reviews.apache.org/r/33828/ we now always add a flag,
regardless of if we don't add {{\-O2}} which is something I should have caught
in my review...). The magic shortcuts are just making these combinations easier
to use and work right (Sort of like how we add very specific flags if we see
you are using compiler X so that mesos builds without needing to manually
specify CXXFLAGS to work around specific compiler versions).
> --enable-optimize build fails with maybe-uninitialized
> ------------------------------------------------------
>
> Key: MESOS-2690
> URL: https://issues.apache.org/jira/browse/MESOS-2690
> Project: Mesos
> Issue Type: Bug
> Components: build
> Environment: GCC 4.8 -> 4.9
> Reporter: Joris Van Remoortere
> Assignee: Joris Van Remoortere
> Priority: Blocker
>
> When building with the `enable-optimize` flag, the build fails with
> `maybe-uninitialized' errors.
> This is due to a bug in GCC when building optimized code triggering false
> positives for this warning. Please see:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59970
> We can disable this warning when using GCC + --enable-optimize.
> A quick work-around until there is a patch:
> ../configure CXXFLAGS="-Wno-maybe-uninitialized" <your-other-flags-here>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
