From: Ian Rogers <irogers@google.com>
To: Pierre Cheynier <p.cheynier@criteo.com>
Cc: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: [6.5.4] perf: bison min. requirements
Date: Tue, 26 Sep 2023 14:28:50 -0700 [thread overview]
Message-ID: <CAP-5=fVPVodcSkOHnJOrgkUO1QOnNTcsPMsfeEKvzjTvqA2K+w@mail.gmail.com> (raw)
In-Reply-To: <PAWPR04MB97658DD9546C6D0A141C0766EAC3A@PAWPR04MB9765.eurprd04.prod.outlook.com>
On Tue, Sep 26, 2023 at 1:21 AM Pierre Cheynier <p.cheynier@criteo.com> wrote:
>
> Dear list,
> At compiling 6.5.4 it seemed to me that this specific patch [1] added an implicit dependency to bison >= 3.7.4, due to usage of YYNOMEM.
> Shouldn't this be part of Documentation/process/changes.rst?
>
> [1] https://www.spinics.net/lists/linux-perf-users/msg30885.html "perf parse-events: Separate YYABORT and YYNOMEM cases"
>
> Sorry for the noise, and thanks for inputs if ever I'm totally wrong here.
We have a workaround to #define YYNOMEM to YYABORT when Bison is
less-than 3.8.1:
https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/tree/tools/perf/util/Build?h=perf-tools-next#n323
Perhaps you can help debug why this build logic isn't working for you?
Thanks,
Ian
> --
> Pierre
next prev parent reply other threads:[~2023-09-26 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 8:21 [6.5.4] perf: bison min. requirements Pierre Cheynier
2023-09-26 21:28 ` Ian Rogers [this message]
2023-09-29 16:42 ` Anisse Astier
2023-09-29 16:45 ` Ian Rogers
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='CAP-5=fVPVodcSkOHnJOrgkUO1QOnNTcsPMsfeEKvzjTvqA2K+w@mail.gmail.com' \
--to=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=p.cheynier@criteo.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;
as well as URLs for NNTP newsgroup(s).