public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] perf tools: Including pre-generated flex files
Date: Thu, 29 Mar 2012 11:37:12 -0300	[thread overview]
Message-ID: <20120329143712.GH8482@infradead.org> (raw)
In-Reply-To: <20120329122208.GC6949@m.brq.redhat.com>

Em Thu, Mar 29, 2012 at 02:22:08PM +0200, Jiri Olsa escreveu:
> I just tried to generate the parser on RHEL6 and got:
> 
>     CC util/parse-events-bison.o
> util/parse-events-bison.c:222:6: error: "YYENABLE_NLS" is not defined
> util/parse-events-bison.c:664:6: error: "YYLTYPE_IS_TRIVIAL" is not
> defined
> 
> looks like bison bug, that RHEL6 did not picked up fix for yet.
> 
> I agree with not including the parser sources in git, but we'll probably
> get some screaming from ppl having similar issue like above.
> 
> Also I'm not fully sure we could even use generated bison/flex
> files cross architectures.. need to check :)

I got yet another error here:

[acme@sandy linux]$ rm -rf ../build/perf/
[acme@sandy linux]$ mkdir ../build/perf/
[acme@sandy linux]$ make -j8 -C tools/perf/ O=/home/git/build/perf
install
make: Entering directory `/home/git/linux/tools/perf'
    MKDIR /home/git/build/perf/arch/x86/util
<SNIP>
    MKDIR /home/git/build/perf/util/ui/browsers
PERF_VERSION = perf.urgent.for.mingo.6.g7e025ca
make: Leaving directory `/home/git/linux/tools/perf'
make: Entering directory `/home/git/linux/tools/perf'
    GEN /home/git/build/perf/common-cmds.h
    * new build flags or prefix
    CC /home/git/build/perf/bench/mem-memcpy-x86-64-asm.o
<SNIP>
    CC /home/git/build/perf/util/trace-event-parse.o
    BISON event-parser
    CC /home/git/build/perf/util/parse-events-bison.o
    FLEX event-parser
    BISON pmu-parser
util/parse-events-bison.c:150:10: error: missing terminating " character
util/parse-events-bison.c:150:10: error: ""util/par" is not a valid
filename
util/parse-events-bison.c:145:1: error: unterminated #if
util/parse-events-bison.c:147: error: expected specifier-qualifier-list
at end of input
make: *** [/home/git/build/perf/util/parse-events-bison.o] Error 1
make: *** Waiting for unfinished jobs....
    FLEX pmu-parser
make: Leaving directory `/home/git/linux/tools/perf'
[acme@sandy linux]$ 

- Arnaldo

  reply	other threads:[~2012-03-29 14:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 18:15 [RFC] perf tools: Including pre-generated flex files Arnaldo Carvalho de Melo
2012-03-27 18:33 ` Ingo Molnar
2012-03-29  6:43   ` Jiri Olsa
2012-03-31  7:47   ` [tip:perf/urgent] perf tools: Remove auto-generated bison/ " tip-bot for Ingo Molnar
2012-03-28 19:46 ` [RFC] perf tools: Including pre-generated " Linus Torvalds
2012-03-29 12:22   ` Jiri Olsa
2012-03-29 14:37     ` Arnaldo Carvalho de Melo [this message]
2012-03-29 14:38     ` Ingo Molnar
2012-03-29 15:45       ` 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=20120329143712.GH8482@infradead.org \
    --to=acme@infradead.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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