linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jiri Olsa <jolsa@kernel.org>, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf tools: Add reject option for parse-events.l
Date: Thu, 9 Nov 2017 10:22:45 -0300	[thread overview]
Message-ID: <20171109132245.GH4333@kernel.org> (raw)
In-Reply-To: <20171109081749.GA21513@krava>

Em Thu, Nov 09, 2017 at 09:17:49AM +0100, Jiri Olsa escreveu:
> Reply-To: 
> In-Reply-To: <20171109081319.GB236@x4>
> 
> On Thu, Nov 09, 2017 at 09:13:19AM +0100, Markus Trippelsdorf wrote:
> > On 2017.11.05 at 15:40 +0100, Ingo Molnar wrote:
> > util/parse-events.l:343:26: note: in expansion of macro ‘USER_REJECT’
> >  {bpf_source}  { if (!isbpf(yyscanner)) USER_REJECT; return str(yyscanner, PE_BPF_SOURCE); }
> >                           ^~~~~~~~~~~
> > mv: cannot stat 'util/.parse-events-flex.o.tmp': No such file or directory
> 
> sry, we have a fix in queue already

yeah, I noticed it while building for Alpine Linux 3.6 and Edge, that
have flex 2.6.4, which is newer than what is in the other distros,
ubuntu, debian, fedora, even their experimental ones (rawhide, etc),
out of curiosity, what distro do you use and what flex version does it
use?

- Arnaldo

  reply	other threads:[~2017-11-09 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09  8:17 [PATCH] perf tools: Add reject option for parse-events.l Jiri Olsa
2017-11-09 13:22 ` Arnaldo Carvalho de Melo [this message]
2017-11-09 13:27   ` Markus Trippelsdorf
2017-11-09 13:51     ` 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=20171109132245.GH4333@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).