All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Wang YanQing <udknight@gmail.com>,
	jolsa@kernel.org, mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools:perf:scripting-engines: Fix compile error with some perl5 versions
Date: Mon, 13 Feb 2017 13:14:35 -0300	[thread overview]
Message-ID: <20170213161435.GA6473@kernel.org> (raw)
In-Reply-To: <20170213081918.GC11147@krava>

Em Mon, Feb 13, 2017 at 09:19:18AM +0100, Jiri Olsa escreveu:
> On Sun, Feb 12, 2017 at 10:46:55AM +0800, Wang YanQing wrote:
> > Fix below compile error:
> > CC       util/scripting-engines/trace-event-perl.o
> > In file included from /usr/lib/perl5/5.22.2/i686-linux/CORE/perl.h:5673:0,
> >                  from util/scripting-engines/trace-event-perl.c:31:
> > /usr/lib/perl5/5.22.2/i686-linux/CORE/inline.h: In function 'S__is_utf8_char_slow':
> > /usr/lib/perl5/5.22.2/i686-linux/CORE/inline.h:270:5: error: nested extern declaration of 'Perl___notused' [-Werror=nested-externs]
> >         dTHX;   /* The function called below requires thread context */
> > 			     ^
> > cc1: all warnings being treated as errors
> > 
> > After digging perl5 repository, I find out that we will meet this compile error
> > with perl from v5.21.1 to v5.25.4
> > 
> > Signed-off-by: Wang YanQing <udknight@gmail.com>
> 
> Acked-by: Jiri Olsa <jolsa@redhat.com>

Thanks, applied.

- Arnaldo

  reply	other threads:[~2017-02-13 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12  2:46 [PATCH] tools:perf:scripting-engines: Fix compile error with some perl5 versions Wang YanQing
2017-02-13  8:19 ` Jiri Olsa
2017-02-13 16:14   ` Arnaldo Carvalho de Melo [this message]
2017-02-14  6:40 ` [tip:perf/core] perf scripting perl: " tip-bot for Wang YanQing

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=20170213161435.GA6473@kernel.org \
    --to=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=udknight@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 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.