From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.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 12:45:11 -0300 [thread overview]
Message-ID: <20120329154511.GI8482@infradead.org> (raw)
In-Reply-To: <20120329143806.GA18890@gmail.com>
Em Thu, Mar 29, 2012 at 04:38:06PM +0200, Ingo Molnar escreveu:
> * Jiri Olsa <jolsa@redhat.com> wrote:
> > 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
>
> Have you first deleted all the autogenerated files via:
>
> rm -f util/pmu-* and util/parse-events-*
>
> ? ['make clean' should also do this - it doesn't, right now.]
>
> Otherwise you could be mixing different versions of the parser
> files.
I don't think so, I discussed this with him and I'm fixing it.
There are several problems, the generate rules weren't obeying O=, etc,
I think I got it fixed, testing now.
- arnaldo
prev parent reply other threads:[~2012-03-29 15:45 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
2012-03-29 14:38 ` Ingo Molnar
2012-03-29 15:45 ` 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=20120329154511.GI8482@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