You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Aaron Wood (JIRA)" <ji...@apache.org> on 2016/12/21 22:07:58 UTC

[jira] [Updated] (MESOS-6829) Mesos fails to compile when using FORTIFY_SOURCE without optimizations

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

Aaron Wood updated MESOS-6829:
------------------------------
    Description: 
Fome some versions of gcc/glibc a warning will be produced with FORTIFY_SOURCE is used without optimizations enabled (see here for related information https://sourceware.org/bugzilla/show_bug.cgi?id=13979). This only happens in some environments such as CentOS 7 and Arch Linux with GCC 6.2.

Probably one of the reasons why it didn't get caught earlier by CI:

"This #warning appears to be causing more grief than it is solving; for example, see this autoconf thread that complains that it is breaking configure scripts, and therefore Debian's decision to revert this patch in their build of glibc:

https://lists.gnu.org/archive/html/autoconf/2013-05/msg00003.html
http://anonscm.debian.org/viewvc/pkg-glibc/glibc-package/trunk/debian/patches/any/local-revert-bz13979.diff?revision=5553&view=markup"

https://reviews.apache.org/r/54949/
https://reviews.apache.org/r/54950/
https://reviews.apache.org/r/54951/

  was:
Fome some versions of gcc/glibc a warning will be produced with FORTIFY_SOURCE is used without optimizations enabled (see here for related information https://sourceware.org/bugzilla/show_bug.cgi?id=13979). This only happens in some environments such as CentOS 7 and Arch Linux with GCC 6.2.

Probably one of the reasons why it didn't get caught earlier by CI:

"This #warning appears to be causing more grief than it is solving; for example, see this autoconf thread that complains that it is breaking configure scripts, and therefore Debian's decision to revert this patch in their build of glibc:

https://lists.gnu.org/archive/html/autoconf/2013-05/msg00003.html
http://anonscm.debian.org/viewvc/pkg-glibc/glibc-package/trunk/debian/patches/any/local-revert-bz13979.diff?revision=5553&view=markup"


> Mesos fails to compile when using FORTIFY_SOURCE without optimizations
> ----------------------------------------------------------------------
>
>                 Key: MESOS-6829
>                 URL: https://issues.apache.org/jira/browse/MESOS-6829
>             Project: Mesos
>          Issue Type: Bug
>          Components: build, libprocess, security, stout
>            Reporter: Aaron Wood
>            Assignee: Aaron Wood
>
> Fome some versions of gcc/glibc a warning will be produced with FORTIFY_SOURCE is used without optimizations enabled (see here for related information https://sourceware.org/bugzilla/show_bug.cgi?id=13979). This only happens in some environments such as CentOS 7 and Arch Linux with GCC 6.2.
> Probably one of the reasons why it didn't get caught earlier by CI:
> "This #warning appears to be causing more grief than it is solving; for example, see this autoconf thread that complains that it is breaking configure scripts, and therefore Debian's decision to revert this patch in their build of glibc:
> https://lists.gnu.org/archive/html/autoconf/2013-05/msg00003.html
> http://anonscm.debian.org/viewvc/pkg-glibc/glibc-package/trunk/debian/patches/any/local-revert-bz13979.diff?revision=5553&view=markup"
> https://reviews.apache.org/r/54949/
> https://reviews.apache.org/r/54950/
> https://reviews.apache.org/r/54951/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)