From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20511 invoked by alias); 24 Nov 2014 00:08:36 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 20462 invoked by uid 48); 24 Nov 2014 00:08:31 -0000 From: "anatol.pomozov at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/13979] A warning should be issued if FORTIFY_SOURCE is requested but not enabled Date: Mon, 24 Nov 2014 00:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.15 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: anatol.pomozov at gmail dot com X-Bugzilla-Status: REOPENED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-11/txt/msg00172.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=13979 Anatol Pomozov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anatol.pomozov at gmail dot com --- Comment #7 from Anatol Pomozov --- Linux Arch still suffers from warnings flood produced by this code. We have following disto-wide compilation variables: CPPFLAGS="-D_FORTIFY_SOURCE=2" CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4" and compilation produces a lot of warnings in almost any c++ project: /usr/include/features.h:328:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp] # warning _FORTIFY_SOURCE requires compiling with optimization (-O) What is the action item for us, downstream package maintainers? What we suppose to do? There were several proposals (see link to autoconf discussion above): - revert commit 05c2c9618f5 - move _FORTIFY_SOURCE to CFLAGS/CXXFLAGS/.. - move -O2 to CPPFLAGS Could you please give us advice on what solution is the best one. -- You are receiving this mail because: You are on the CC list for the bug.