public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf tools: Fix bison-related build failure on CentOS 6
Date: Wed, 29 Apr 2015 15:47:54 -0300	[thread overview]
Message-ID: <20150429184754.GA2200@redhat.com> (raw)
In-Reply-To: <20150429181414.GA14167@krava.redhat.com>

Em Wed, Apr 29, 2015 at 08:14:14PM +0200, Jiri Olsa escreveu:
> On Wed, Apr 29, 2015 at 07:57:05PM +0200, Jiri Olsa wrote:
> > On Wed, Apr 29, 2015 at 01:27:40PM -0300, Arnaldo Carvalho de Melo wrote:
> > > > The YYLTYPE_IS_TRIVIAL is defined in the Build file, but unlike
> > > > pmu-bison.c, gcc complained about it for parse-events-bison.c:
> > > > 
> > > >     CC       util/parse-events-bison.o
> > > >   In file included from util/parse-events.y:16:
> > > >   util/parse-events-bison.h:101:1: error: "YYLTYPE_IS_TRIVIAL" redefined
> > > >   <command-line>: error: this is the location of the previous definition
> > > >   make[3]: *** [util/parse-events-bison.o] Error 1
> > > > 
> > > > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > > 
> > > Ok, so this helps, it builds now on RHEL6.6, which was something I and
> > > Jiri were chasing, but why has it complained for one and not the other?
> > > Ideas?
> > 
> > looks like the RHEL6 gcc/cpp treats this as an error which
> > is not maskable by '-w' option
> > 
> > anyway I checked the git log history and I'm not sure
> > why we event have this define, it was added by Ingo
> > and carried by ever since:
> > 
> >   65f3e56e0c81 perf tools: Remove auto-generated bison/flex files
> > 
> > probably because of the fail I see if I remove it from pmu-bison.o build:
> > 
> >   util/pmu-bison.c:613:6: error: "YYLTYPE_IS_TRIVIAL" is not defined
> 
> ok, seem's the patch is right and the reason is the
> parse error handling that was added just recently
> 
> it adds YYLTYPE type (which is not present in pmu-bison.h),
> so YYLTYPE_IS_TRIVIAL gets redefined, which is ok in F20
> that handle the error via '-w' option, but it's not ok for RHEL6
> where the '-w' does not work for this kind of error

Ok, adding this comment to the changelog, together with your Acked-by,
ok?

- Arnaldo

  reply	other threads:[~2015-04-29 18:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 15:54 [PATCH] perf tools: Fix bison-related build failure on CentOS 6 Namhyung Kim
2015-04-29 16:02 ` Jiri Olsa
2015-04-29 16:11   ` Namhyung Kim
2015-04-29 16:47     ` Arnaldo Carvalho de Melo
2015-04-29 16:27 ` Arnaldo Carvalho de Melo
2015-04-29 17:57   ` Jiri Olsa
2015-04-29 18:14     ` Jiri Olsa
2015-04-29 18:47       ` Arnaldo Carvalho de Melo [this message]
2015-04-29 19:14         ` Jiri Olsa
2015-05-06  3:12 ` [tip:perf/core] " 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=20150429184754.GA2200@redhat.com \
    --to=acme@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.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