From: Richard Weinberger <richard@sigma-star.at>
To: Randy Dunlap <rdunlap@infradead.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 4.15-rc3 (uml + bpf_perf_event.h)
Date: Mon, 11 Dec 2017 09:32:38 +0100 [thread overview]
Message-ID: <7534692.EB8JgYtGIt@blindfold> (raw)
In-Reply-To: <4a55b480-a35b-1432-95d6-079857bceca5@infradead.org>
Randy,
Am Montag, 11. Dezember 2017, 03:42:12 CET schrieb Randy Dunlap:
> On 12/10/2017 06:08 PM, Linus Torvalds wrote:
> > Another week, another rc.
>
> um (uml) won't build on i386 or x86_64:
>
> CC init/main.o
> In file included from ../include/linux/perf_event.h:18:0,
> from ../include/linux/trace_events.h:10,
> from ../include/trace/syscall.h:7,
> from ../include/linux/syscalls.h:82,
> from ../init/main.c:20:
> ../include/uapi/linux/bpf_perf_event.h:11:32: fatal error:
> asm/bpf_perf_event.h: No such file or directory #include
> <asm/bpf_perf_event.h>
> ^
> compilation terminated.
> ../scripts/Makefile.build:310: recipe for target 'init/main.o' failed
>
How do you trigger that build failure?
Can you share your .config?
Thanks,
//richard
--
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y
next prev parent reply other threads:[~2017-12-11 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 2:08 Linux 4.15-rc3 Linus Torvalds
2017-12-11 2:42 ` Linux 4.15-rc3 (uml + bpf_perf_event.h) Randy Dunlap
2017-12-11 8:32 ` Richard Weinberger [this message]
2017-12-11 10:19 ` Daniel Borkmann
2017-12-11 17:27 ` Randy Dunlap
2017-12-11 17:32 ` Daniel Borkmann
2017-12-11 18:19 ` Richard Weinberger
2017-12-11 18:49 ` Richard Weinberger
2017-12-11 18:56 ` Randy Dunlap
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=7534692.EB8JgYtGIt@blindfold \
--to=richard@sigma-star.at \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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 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.