From: Andi Kleen <andi@firstfloor.org>
To: acme@ghostprotocols.net, jolsa@redhat.com,
Zheng Yan <zheng.z.yan@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Current perf tool does not compile anymore on RHEL6
Date: Tue, 18 Sep 2012 10:29:48 -0700 [thread overview]
Message-ID: <m2fw6fxmr7.fsf@firstfloor.org> (raw)
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.
CC /home/ak/lsrc/obj-perf/util/symbol.o
util/parse-events.c: In function ‘parse_events__scanner’:
util/parse-events.c:695: warning: implicit declaration of function
‘parse_events_lex_init_extra’
util/parse-events.c:695: warning: nested extern declaration of
‘parse_events_lex_init_extra’
util/parse-events.c:699: error: too many arguments to function
‘parse_events__scan_string’
util/parse-events.c:706: error: too many arguments to function
‘parse_events__flush_buffer’
util/parse-events.c:707: error: too many arguments to function
‘parse_events__delete_buffer’
util/parse-events.c:708: error: too many arguments to function
‘parse_events_lex_destroy’
util/parse-events.c: In function ‘parse_events_terms’:
util/parse-events.c:722: error: ‘PE_START_TERMS’ undeclared (first use
in this function)
util/parse-events.c:722: error: (Each undeclared identifier is reported
only once
util/parse-events.c:722: error: for each function it appears in.)
util/parse-events.c: In function ‘parse_events’:
util/parse-events.c:741: error: ‘PE_START_EVENTS’ undeclared (first use
in this function)
--
ak@linux.intel.com -- Speaking for myself only
next reply other threads:[~2012-09-18 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 17:29 Andi Kleen [this message]
2012-09-18 17:38 ` Current perf tool does not compile anymore on RHEL6 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
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=m2fw6fxmr7.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@ghostprotocols.net \
--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