From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kees Cook <keescook@chromium.org>
Cc: Andrei Vagin <avagin@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the seccomp tree
Date: Thu, 29 Jun 2023 12:40:55 +1000 [thread overview]
Message-ID: <20230629124055.7edf4493@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
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")
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-06-29 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 2:40 Stephen Rothwell [this message]
2023-06-29 5:27 ` linux-next: build failure after merge of the seccomp tree Andrei Vagin
2023-06-29 5:30 ` Kees Cook
2023-06-29 5:58 ` Kees Cook
2023-06-30 5:22 ` Andrei Vagin
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=20230629124055.7edf4493@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=avagin@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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