From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: linux-kbuild@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
Michal Marek <mmarek@suse.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH] kbuild: List libelf-devel as an alternative
Date: Thu, 16 Jun 2016 10:08:09 -0500 [thread overview]
Message-ID: <20160616150809.f3tdj6hxdbypbboc@treble> (raw)
In-Reply-To: <20160616105420.13b4dbf2@endymion>
On Thu, Jun 16, 2016 at 10:54:20AM +0200, Jean Delvare wrote:
> On openSUSE, the libelf development files are in package libelf-devel.
>
> Signed-off-by: Jean Delare <jdelvare@suse.de>
> Cc: Josh Poimboeuf <jpoimboe@redhat.com>
> Cc: Jiri Olsa <jolsa@redhat.com>
> Cc: Michal Marek <mmarek@suse.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
> ---
> Makefile | 2 +-
> tools/perf/config/Makefile | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-4.6.orig/Makefile 2016-05-16 00:43:13.000000000 +0200
> +++ linux-4.6/Makefile 2016-06-16 10:42:26.990587718 +0200
> @@ -1013,7 +1013,7 @@ ifdef CONFIG_STACK_VALIDATION
> ifeq ($(has_libelf),1)
> objtool_target := tools/objtool FORCE
> else
> - $(warning "Cannot use CONFIG_STACK_VALIDATION, please install libelf-dev or elfutils-libelf-devel")
> + $(warning "Cannot use CONFIG_STACK_VALIDATION, please install libelf-dev, libelf-devel or elfutils-libelf-devel")
> SKIP_STACK_VALIDATION := 1
> export SKIP_STACK_VALIDATION
> endif
> --- linux-4.6.orig/tools/perf/config/Makefile 2016-05-16 00:43:13.000000000 +0200
> +++ linux-4.6/tools/perf/config/Makefile 2016-06-16 10:43:29.517409971 +0200
> @@ -243,7 +243,7 @@ else
> LIBC_SUPPORT := 1
> endif
> ifeq ($(LIBC_SUPPORT),1)
> - msg := $(warning No libelf found, disables 'probe' tool and BPF support in 'perf record', please install elfutils-libelf-devel/libelf-dev);
> + msg := $(warning No libelf found, disables 'probe' tool and BPF support in 'perf record', please install libelf-dev, libelf-devel or elfutils-libelf-devel);
>
> NO_LIBELF := 1
> NO_DWARF := 1
>
>
> --
> Jean Delvare
> SUSE L3 Support
--
Josh
next prev parent reply other threads:[~2016-06-16 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 8:54 [PATCH] kbuild: List libelf-devel as an alternative Jean Delvare
2016-06-16 15:08 ` Josh Poimboeuf [this message]
2016-06-16 16:38 ` Arnaldo Carvalho de Melo
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=20160616150809.f3tdj6hxdbypbboc@treble \
--to=jpoimboe@redhat.com \
--cc=acme@kernel.org \
--cc=jdelvare@suse.de \
--cc=jolsa@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox