From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: "Andrii Nakryiko" <andrii.nakryiko@gmail.com>,
"Andrii Nakryiko" <andriin@fb.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
BPF-dev-list <bpf@vger.kernel.org>,
"Alexei Starovoitov" <alexei.starovoitov@gmail.com>,
"Daniel Borkmann" <borkmann@iogearbox.net>,
"David Miller" <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Toke Høiland-Jørgensen" <toke@redhat.com>
Subject: Re: Kernel 5.5.4 build fail for BPF-selftests with latest LLVM
Date: Wed, 19 Feb 2020 14:28:56 +0100 [thread overview]
Message-ID: <20200219132856.GA2836367@kroah.com> (raw)
In-Reply-To: <20200219133012.7cb6ac9e@carbon>
On Wed, Feb 19, 2020 at 01:30:12PM +0100, Jesper Dangaard Brouer wrote:
> Hi Andrii,
>
> Downloaded tarball for kernel release 5.5.4, and I cannot compile
> tools/testing/selftests/bpf/ with latest LLVM release version 9.
Is this something that recently broke? If so, what commit caused it?
And has llvm 9 always worked here?
> Looking closer at the build error messages, I can see that this is
> caused by using LLVM features that (I assume) will be avail in release
> 10. I find it very strange that we can release a kernel that have build
> dependencies on a unreleased version of LLVM.
Is this the first time you have tried using llvm to build a kernel?
This isn't a new thing :)
> I love the new LLVM BTF features, but we cannot break users/CI-systems
> that wants to run the BPF-selftests.
Is this a regression from older kernels?
And does gcc work?
thanks,
greg k-h
next prev parent reply other threads:[~2020-02-19 13:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 12:30 Kernel 5.5.4 build fail for BPF-selftests with latest LLVM Jesper Dangaard Brouer
2020-02-19 13:28 ` Greg Kroah-Hartman [this message]
2020-02-19 13:42 ` Jesper Dangaard Brouer
2020-02-19 18:12 ` Greg Kroah-Hartman
2020-02-19 19:40 ` Jesper Dangaard Brouer
2020-02-19 20:20 ` Greg Kroah-Hartman
2020-02-19 16:41 ` Alexei Starovoitov
2020-02-19 17:03 ` Jesper Dangaard Brouer
2020-02-19 17:38 ` Andrii Nakryiko
2020-02-19 18:28 ` Jesper Dangaard Brouer
2020-02-19 18:38 ` Andrii Nakryiko
2020-02-19 20:06 ` Jesper Dangaard Brouer
2020-02-19 21:59 ` Daniel Díaz
2020-02-19 22:26 ` Andrii Nakryiko
2020-02-20 0:27 ` Alexei Starovoitov
2020-02-20 0:47 ` shuah
2020-02-20 16:37 ` Jesper Dangaard Brouer
2020-02-20 17:02 ` Bird, Tim
2020-02-20 17:26 ` Alexei Starovoitov
2020-02-20 17:41 ` Bird, Tim
2020-02-20 19:18 ` Alexei Starovoitov
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=20200219132856.GA2836367@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=borkmann@iogearbox.net \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.com \
/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.