All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the perf tree
Date: Thu, 27 Mar 2025 23:40:18 -0700	[thread overview]
Message-ID: <Z-ZEUtZJPZ4BwA5r@google.com> (raw)
In-Reply-To: <20250327102234.50ad6e84@canb.auug.org.au>

Hello,

On Thu, Mar 27, 2025 at 10:22:34AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the perf tree, today's linux-next build (native ppc perf)
> failed like this:
> 
> perf/util/bpf-filter-flex.c:2245:1: error: unterminated comment
>  2245 | /** Pushes the new state onto the stack. The new state becomes
>       | ^
> perf/util/bpf-filter-flex.c:20:31: error: 'perf_bpf_filter_ensure_buffer_stack' used but never defined [-Werror]
>    20 | #define yyensure_buffer_stack perf_bpf_filter_ensure_buffer_stack
>       |                               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> perf/util/bpf-filter-flex.c:550:13: note: in expansion of macro 'yyensure_buffer_stack'
>   550 | static void yyensure_buffer_stack ( void );
>       |             ^~~~~~~~~~~~~~~~~~~~~
> perf/util/bpf-filter-flex.c:606:24: error: 'yy_fatal_error' used but never defined [-Werror]
>   606 | static void yynoreturn yy_fatal_error ( const char* msg  );
>       |                        ^~~~~~~~~~~~~~
> perf/util/bpf-filter-flex.c:510:15: error: 'yy_buffer_stack_max' defined but not used [-Werror=unused-variable]
>   510 | static size_t yy_buffer_stack_max = 0; /**< capacity of stack. */
>       |               ^~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
> 
> I don't know what caused this, but simply rebuilding worked.  So maybe
> some dependency is missing in the make files?

Strange, but it seems so.  I'll take a look if I missed something.
Thanks for the report and your hard work!

Namhyung


  reply	other threads:[~2025-03-28  6:40 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 23:22 linux-next: build failure after merge of the perf tree Stephen Rothwell
2025-03-28  6:40 ` Namhyung Kim [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-19 16:09 Mark Brown
2026-01-19 16:37 ` James Clark
2026-01-19 16:43   ` Mark Brown
2026-01-19 16:55     ` James Clark
2026-01-19 17:02       ` Mark Brown
2026-01-26 15:13 ` Mark Brown
2026-01-26 15:20   ` James Clark
2025-02-14  4:20 Stephen Rothwell
2025-01-09 23:05 Stephen Rothwell
2025-01-09 23:31 ` Charlie Jenkins
2025-01-10 14:01   ` Arnaldo Carvalho de Melo
2025-01-10 17:32     ` Arnaldo Carvalho de Melo
2025-01-10 18:59       ` Charlie Jenkins
2025-01-10 19:22     ` Charlie Jenkins
2024-10-10 23:23 Stephen Rothwell
2024-09-05  1:55 Stephen Rothwell
2024-04-01 22:41 Stephen Rothwell
2024-04-02 20:17 ` Arnaldo Carvalho de Melo
2024-04-12 15:22 ` Arnaldo Carvalho de Melo
2024-04-13  2:43   ` Stephen Rothwell
2024-03-21 21:41 Stephen Rothwell
2024-03-21 23:18 ` Arnaldo Carvalho de Melo
2024-03-21 23:19   ` Arnaldo Carvalho de Melo
2024-03-21 23:32     ` Stephen Rothwell
2024-03-22  2:13       ` Stephen Rothwell
2024-03-22 14:32         ` Arnaldo Carvalho de Melo
2024-03-21 23:36   ` Stephen Rothwell
2024-03-21 23:40     ` arnaldo.melo
2024-03-21 23:48     ` Arnaldo Carvalho de Melo
2024-02-21 23:06 Stephen Rothwell
2024-02-23 19:50 ` Arnaldo Carvalho de Melo
2024-02-06 23:40 Stephen Rothwell
2024-02-07  0:02 ` Ian Rogers
2023-10-24 23:26 Stephen Rothwell
2023-10-25  0:34 ` Namhyung Kim
2023-05-29 23:05 Stephen Rothwell
2023-05-30  2:16 ` Ian Rogers
2023-03-16 22:50 Stephen Rothwell
2023-03-16 23:11 ` Arnaldo Carvalho de Melo
2023-03-16 23:55   ` Stephen Rothwell
2023-03-17  3:23     ` Ian Rogers
2023-03-21 21:39 ` Stephen Rothwell
2023-03-22 18:37   ` Ian Rogers
2023-03-22 22:54     ` Stephen Rothwell
2023-03-23 13:27       ` Arnaldo Carvalho de Melo
2023-03-27 20:31         ` Ian Rogers
2023-03-28  1:33         ` Stephen Rothwell
2023-03-28 19:47           ` Arnaldo Carvalho de Melo
2023-03-28 23:06             ` Stephen Rothwell
2023-03-29 12:28               ` Arnaldo Carvalho de Melo
2023-04-03  5:15                 ` Stephen Rothwell
2022-08-30 22:34 Stephen Rothwell
2022-09-01  5:11 ` Anshuman Khandual
2022-09-06 19:05 ` Stephen Rothwell
2022-09-07  2:31   ` Anshuman Khandual
2022-09-07  3:00     ` Stephen Rothwell
2022-09-07  4:22       ` Anshuman Khandual
2022-09-08 15:21         ` Arnaldo Carvalho de Melo
2022-07-20 23:05 Stephen Rothwell
2022-07-21  2:35 ` Ian Rogers
2022-07-21  3:55   ` Stephen Rothwell
2022-07-21  5:33     ` Ian Rogers
2022-01-05 22:19 Stephen Rothwell
2022-01-07  8:58 ` kajoljain
2022-01-11 21:45   ` Stephen Rothwell
2022-01-11 22:01     ` Arnaldo Carvalho de Melo
2022-01-12  5:30       ` kajoljain
2022-01-12  6:16       ` Stephen Rothwell
2022-01-14 12:03       ` Michael Ellerman

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=Z-ZEUtZJPZ4BwA5r@google.com \
    --to=namhyung@kernel.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.