[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANaxB-z0gLxOU-EVnag=pi3cC164stbOVOMmaGMwNs_g43z9_w@mail.gmail.com>
Date: Wed, 28 Jun 2023 22:27:09 -0700
From: Andrei Vagin <avagin@...il.com>
To: Kees Cook <keescook@...omium.org>
Cc: Andrei Vagin <avagin@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: linux-next: build failure after merge of the seccomp tree
On Wed, Jun 28, 2023 at 7:50 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> After merging the seccomp tree, today's linux-next build (native perf)
> failed like this:
>
> make[3]: *** No rule to make target '/home/sfr/next/perf/bench/sched-seccomp-notify.o', needed by '/home/sfr/next/perf/bench/perf-in.o'. Stop.
> make[3]: *** Waiting for unfinished jobs....
> make[2]: *** [/home/sfr/next/next/tools/build/Makefile.build:140: bench] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [Makefile.perf:682: /home/sfr/next/perf/perf-in.o] Error 2
> make: *** [Makefile.perf:242: sub-make] Error 2
> Command exited with non-zero status 2
>
> Presumably caused by commit
>
> df614e369b5c ("perf/benchmark: add a new benchmark for seccom_unotify")
tools/perf/bench/sched-seccomp-notify.c should be in this commit too.
Probably something went wrong when the patch was applied. I've checked
that the patch contains this file:
https://patchew.org/linux/20230308073201.3102738-1-avagin@google.com/20230308073201.3102738-7-avagin@google.com/
Kees, could you take a look at this?
>
> This is a native build of perf on a PowerPC 46 bit LE host.
>
> I have used the seccomp tree from next-20230628 for today.
>
> --
> Cheers,
> Stephen Rothwell
Powered by blists - more mailing lists