public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Zheng Yan <zheng.z.yan@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Current perf tool does not compile anymore on RHEL6
Date: Mon, 24 Sep 2012 06:12:49 -0700	[thread overview]
Message-ID: <20120924131249.GG22954@ghostprotocols.net> (raw)
In-Reply-To: <20120924120529.GJ989@krava.brq.redhat.com>

Em Mon, Sep 24, 2012 at 02:05:29PM +0200, Jiri Olsa escreveu:
> On Mon, Sep 24, 2012 at 12:28:04PM +0200, Jiri Olsa wrote:
> > On Tue, Sep 18, 2012 at 10:29:48AM -0700, Andi Kleen wrote:
> > > Presumably flex-2.5.35-8.el6.x86_64 doesn't support YY_EXTRA
> > > 
> > > Problem started with

> > > commit 90e2b22dee908c13df256140a0d6527e3e8ea3f4
> > > Author: Jiri Olsa <jolsa@redhat.com>
> > > Date:   Fri Jun 15 14:31:40 2012 +0800
> > > 
> > >     perf/tool: Add support to reuse event grammar to parse out terms

> > > Unfortunately needs several other patches reverted too to revert.
> > 
> > sry for late answer I was out last week,

> > it's strange since we build 6.3 perf on regular basis,
> > I'll check..
> 
> hm, it builds ok for me with:
> 
> # rpm -qa | egrep "(flex|bison)"
> flex-2.5.35-8.el6.x86_64
> bison-2.4.1-5.el6.x86_64
> 
> Do you still have the issue?

Possibly fixed by a patch by Eric Sandeen, see:

https://lkml.org/lkml/2012/9/20/691

- Arnaldo

      reply	other threads:[~2012-09-24 13:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 17:29 Current perf tool does not compile anymore on RHEL6 Andi Kleen
2012-09-18 17:38 ` Arnaldo Carvalho de Melo
2012-09-24 10:28 ` Jiri Olsa
2012-09-24 12:05   ` Jiri Olsa
2012-09-24 13:12     ` Arnaldo Carvalho de Melo [this message]

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=20120924131249.GG22954@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=andi@firstfloor.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zheng.z.yan@intel.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