linux-kernel - linux-next: build failure after merge of the perf tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20231025102647.321c6629@canb.auug.org.au>
Date:   Wed, 25 Oct 2023 10:26:47 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>,
        Namhyung Kim <namhyung@...nel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: build failure after merge of the perf tree

Hi all,

After merging the perf tree, today's linux-next build (native perf)
failed like this:

perf/util/pmu-flex.c:1812:1: error: unterminated comment
 1812 | /** Setup the input buffer state to scan a string. The next call to yylex() will
      | ^
perf/util/pmu-flex.c:550:24: error: 'yy_fatal_error' used but never defined [-Werror]
  550 | static void yynoreturn yy_fatal_error ( const char* msg , yyscan_t yyscanner );
      |                        ^~~~~~~~~~~~~~

I don't know what caused this, but the above file looks fine and redoing
the build works, so it may be some timing problem when doing an
incremental build?

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped