lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 25 Aug 2020 11:20:20 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Networking <netdev@...r.kernel.org>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
David Miller <davem@...emloft.net>
Subject: Re: linux-next: build failure after merge of the bpf-next tree
Hi all,
On Fri, 21 Aug 2020 11:11:11 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> After merging the bpf-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> Auto-detecting system features:
> ... libelf: [ .[31mOFF.[m ]
> ... zlib: [ .[31mOFF.[m ]
> ... bpf: [ .[32mon.[m ]
>
> No libelf found
> make[5]: *** [Makefile:284: elfdep] Error 1
>
> Caused by commit
>
> d71fa5c9763c ("bpf: Add kernel module with user mode driver that populates bpffs.")
>
> [For a start, can we please *not* add this verbose feature detection
> output to the nrormal build?]
>
> This is a PowerPC hosted cross build.
>
> I have marked BPF_PRELOAD as BROKEN for now.
Still getting this failure ...
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists