From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf tools: Fix build failture on perl script context
Date: Tue, 2 Aug 2016 11:12:32 -0300 [thread overview]
Message-ID: <20160802141232.GB9647@kernel.org> (raw)
In-Reply-To: <20160802140302.GA6968@danjae.aot.lge.com>
Em Tue, Aug 02, 2016 at 11:03:02PM +0900, Namhyung Kim escreveu:
> Hi Arnaldo,
>
> On Tue, Aug 02, 2016 at 10:29:22AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Aug 02, 2016 at 11:43:17AM +0900, Namhyung Kim escreveu:
> > > On my Archlinux machine, perf faild to build like below:
> > >
> > > CC scripts/perl/Perf-Trace-Util/Context.o
> > > In file included from /usr/lib/perl5/core/perl/CORE/perl.h:3905:0,
> > > from Context.xs:23:
> > > /usr/lib/perl5/core/perl/CORE/inline.h: In function :
> > > /usr/lib/perl5/core/perl/CORE/cop.h:612:13: warning: declaration of 'av'
> > > shadows a previous local [-Werror-shadow]
> > > AV *av =3D GvAV(PL_defgv);
> > > ^
> > > /usr/lib/perl5/core/perl/CORE/inline.h:526:5: note: in expansion of
> > > macro 'CX_POP_SAVEARRAY'
> > > CX_POP_SAVEARRAY(cx);
> > > ^~~~~~~~~~~~~~~~
> > > In file included from /usr/lib/perl5/core/perl/CORE/perl.h:5853:0,
> > > from Context.xs:23:
> > > /usr/lib/perl5/core/perl/CORE/inline.h:518:9: note:
> > > shadowed declaration is here
> > > AV *av;
> > > ^~
> >
> > But you forgot to describe _what_ you did to "fix" the problem besides
> > breaking down a long line, i.e. adding -Wno-shadow, is that what we
> > want? To ignore such warnings?
> >
> > Some explanation in the changelog as to why that is the wise solution
> > would help a lot :-\
>
> Oops, sorry.
>
> What I did to fix is adding '-Wno-shadow' as the error message said
> it's the cause of the failure. Since it's from the perl (not perf)
> code base, we don't have the control so I just wanted to ignore the
> warning when compiling perl scripting code.
>
> Is it ok for you?
Now it is :-)
I'll stick this to the changeset log as the reason for adding
-wno-shadow just for building the perl code.
Sometimes we'll get to this conclusion after some thinking, if you add
these explanations to the changelog then it speeds up reviewing.
Thanks,
- Arnaldo
> Thanks,
> Namhyung
>
>
> > >
> > > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > > ---
> > > tools/perf/scripts/perl/Perf-Trace-Util/Build | 4 +++-
> > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/tools/perf/scripts/perl/Perf-Trace-Util/Build b/tools/perf/scripts/perl/Perf-Trace-Util/Build
> > > index 928e110179cb..34faecf774ae 100644
> > > --- a/tools/perf/scripts/perl/Perf-Trace-Util/Build
> > > +++ b/tools/perf/scripts/perl/Perf-Trace-Util/Build
> > > @@ -1,3 +1,5 @@
> > > libperf-y += Context.o
> > >
> > > -CFLAGS_Context.o += $(PERL_EMBED_CCOPTS) -Wno-redundant-decls -Wno-strict-prototypes -Wno-unused-parameter -Wno-nested-externs -Wno-undef -Wno-switch-default
> > > +CFLAGS_Context.o += $(PERL_EMBED_CCOPTS) -Wno-redundant-decls -Wno-strict-prototypes
> > > +CFLAGS_Context.o += -Wno-unused-parameter -Wno-nested-externs -Wno-undef
> > > +CFLAGS_Context.o += -Wno-switch-default -Wno-shadow
> > > --
> > > 2.9.2
next prev parent reply other threads:[~2016-08-02 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 2:43 [PATCH] perf tools: Fix build failture on perl script context Namhyung Kim
2016-08-02 13:26 ` Arnaldo Carvalho de Melo
2016-08-02 13:29 ` Arnaldo Carvalho de Melo
2016-08-02 14:03 ` Namhyung Kim
2016-08-02 14:12 ` Arnaldo Carvalho de Melo [this message]
2016-08-02 15:10 ` Arnaldo Carvalho de Melo
2016-08-04 9:10 ` [tip:perf/urgent] perf tools: Fix build failure " tip-bot for Namhyung Kim
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=20160802141232.GB9647@kernel.org \
--to=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--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