From: Sergei Trofimovich <slyich@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Sergei Trofimovich <slyfox@gentoo.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: [PATCH] tools/perf/Makefile: drop _FORTIFY_SOURCE right before redefinition
Date: Fri, 22 Feb 2013 13:17:54 +0300 [thread overview]
Message-ID: <1361528274-27126-1-git-send-email-slyich@gmail.com> (raw)
From: Sergei Trofimovich <slyfox@gentoo.org>
Gentoo's toolchain sets _FORTIFY_SOURCE by default
which leads to very obscure error:
perf # make clean && make
Makefile:455: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev
Makefile:470: *** No gnu/libc-version.h found, please install glibc-dev[el]/glibc-static. Stop
Patch explicitely undefines _FORTIFY_SOURCE. Thanks!
CC: Peter Zijlstra <a.p.zijlstra@chello.nl>
CC: Paul Mackerras <paulus@samba.org>
CC: Ingo Molnar <mingo@redhat.com>
CC: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
---
tools/perf/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/Makefile b/tools/perf/Makefile
index 891bc77..60f083d 100644
--- a/tools/perf/Makefile
+++ b/tools/perf/Makefile
@@ -94,7 +94,7 @@ ifeq ("$(origin DEBUG)", "command line")
PERF_DEBUG = $(DEBUG)
endif
ifndef PERF_DEBUG
- CFLAGS_OPTIMIZE = -O6 -D_FORTIFY_SOURCE=2
+ CFLAGS_OPTIMIZE = -O6 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
endif
ifdef PARSER_DEBUG
--
1.8.0
next reply other threads:[~2013-02-22 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 10:17 Sergei Trofimovich [this message]
2013-02-22 15:08 ` [PATCH] tools/perf/Makefile: drop _FORTIFY_SOURCE right before redefinition Arnaldo Carvalho de Melo
2013-02-23 11:34 ` Sergei Trofimovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1361528274-27126-1-git-send-email-slyich@gmail.com \
--to=slyich@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=slyfox@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.