From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Sergei Trofimovich <slyich@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Sergei Trofimovich <slyfox@gentoo.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] tools/perf/Makefile: drop _FORTIFY_SOURCE right before redefinition
Date: Fri, 22 Feb 2013 12:08:14 -0300 [thread overview]
Message-ID: <20130222150814.GD18567@ghostprotocols.net> (raw)
In-Reply-To: <1361528274-27126-1-git-send-email-slyich@gmail.com>
Em Fri, Feb 22, 2013 at 01:17:54PM +0300, Sergei Trofimovich escreveu:
> 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!
There was a fix merged recently related to this define, can you please
check?
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
branch
perf/core
This patch:
http://git.kernel.org/?p=linux/kernel/git/acme/linux.git;a=commitdiff;h=1807606ac70da5cda870362c13e71d60e94f9c13
- Arnaldo
next prev parent reply other threads:[~2013-02-22 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 10:17 [PATCH] tools/perf/Makefile: drop _FORTIFY_SOURCE right before redefinition Sergei Trofimovich
2013-02-22 15:08 ` Arnaldo Carvalho de Melo [this message]
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=20130222150814.GD18567@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=slyfox@gentoo.org \
--cc=slyich@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox