From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Vinson Lee <vlee@freedesktop.org>
Cc: linux-next@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Wang Nan <wangnan0@huawei.com>,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: next-20160208 perf build error "tests/bp_signal.c:106:47: error: declaration of ‘signal’ shadows a global declaration [-Werror=shadow]"
Date: Thu, 11 Feb 2016 19:21:21 -0300 [thread overview]
Message-ID: <20160211222121.GK32168@kernel.org> (raw)
In-Reply-To: <CACKvgLFaZagkvRk1R2Xy0=UbWcfELgLxPbfjhRNZj-Rg4jSz4w@mail.gmail.com>
Em Mon, Feb 08, 2016 at 10:28:53AM -0800, Vinson Lee escreveu:
> Hi.
>
> I hit this perf build error with next-20160208 with GCC 4.6.
I try to test on a rhel6 vm from time to time, need to do it using
docker or something, thanks for the report, but can you please send a
proper patch, with a:
Fixes: 6a7d550e8b2e ("perf test: Check environment before start real BPF test")
Line, signed-off, etc?
Thanks,
- Arnaldo
> CC tests/bp_signal.o
> tests/bp_signal.c: In function ‘__event’:
> tests/bp_signal.c:106:47: error: declaration of ‘signal’ shadows a
> global declaration [-Werror=shadow]
> tests/bp_signal.c: In function ‘bp_event’:
> tests/bp_signal.c:144:37: error: declaration of ‘signal’ shadows a
> global declaration [-Werror=shadow]
> tests/bp_signal.c: In function ‘wp_event’:
> tests/bp_signal.c:149:37: error: declaration of ‘signal’ shadows a
> global declaration [-Werror=shadow]
>
> The build error is introduced with "perf test: Check environment
> before start real BPF test".
>
> commit 6a7d550e8b2eeb380ab85d9bc53571123b98345b
> Author: Wang Nan <wangnan0@huawei.com>
> Date: Mon Jan 25 09:55:53 2016 +0000
>
> perf test: Check environment before start real BPF test
>
> Copying perf to old kernel system results:
>
> # perf test bpf
> 37: Test BPF filter :
> 37.1: Test basic BPF filtering : FAILED!
> 37.2: Test BPF prologue generation : Skip
>
> However, in case when kernel doesn't support a test case it should
> return 'Skip', 'FAILED!' should be reserved for kernel tests for when
> the kernel supports a feature that then fails to work as advertised.
>
> This patch checks environment before real testcase.
>
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> Suggested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Alexei Starovoitov <ast@kernel.org>
> Cc: Brendan Gregg <brendan.d.gregg@gmail.com>
> Cc: Daniel Borkmann <daniel@iogearbox.net>
> Cc: He Kuang <hekuang@huawei.com>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Li Zefan <lizefan@huawei.com>
> Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: pi3orama@163.com
> Link: http://lkml.kernel.org/r/1453715801-7732-7-git-send-email-wangnan0@huawei.com
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Cheers,
> Vinson
next prev parent reply other threads:[~2016-02-11 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 18:28 next-20160208 perf build error "tests/bp_signal.c:106:47: error: declaration of ‘signal’ shadows a global declaration [-Werror=shadow]" Vinson Lee
2016-02-11 22:21 ` Arnaldo Carvalho de Melo [this message]
2016-02-12 21:40 ` 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=20160211222121.GK32168@kernel.org \
--to=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vlee@freedesktop.org \
--cc=wangnan0@huawei.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;
as well as URLs for NNTP newsgroup(s).