[
https://issues.apache.org/jira/browse/MESOS-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531438#comment-14531438
]
Vinod Kone commented on MESOS-2690:
-----------------------------------
FWIW, I tested the following patch on OSX and CentOS and it seemed to fix the
regression. I propose we go with this patch until someone tells us this is
unsafe or the gcc bug is fixed. Thoughts?
{code}
+ # Disable 'maybe-uninitialized' warning when "-O2" is enabled due
+ # to MESOS-2690.
+ case $CXXFLAGS in
+ *-O2*) CXXFLAGS="${CXXFLAGS} -Wno-maybe-uninitialized" ;;
+ *) ;;
+ esac
+
{code}
> --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)
