[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210312120014.62ced6dd@canb.auug.org.au>
Date: Fri, 12 Mar 2021 12:00:14 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Björn Töpel <bjorn.topel@...el.com>
Cc: Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Networking <netdev@...r.kernel.org>,
Andrii Nakryiko <andrii@...nel.org>,
Björn Töpel <bjorn@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Masahiro Yamada <masahiroy@...nel.org>
Subject: Re: linux-next: build failure after merge of the bpf-next tree
Hi Björn,
[Cc'ing a few (maybe) interested parties]
On Thu, 11 Mar 2021 07:47:03 +0100 Björn Töpel <bjorn.topel@...el.com> wrote:
>
> On 2021-03-11 01:47, Stephen Rothwell wrote:
> >
> > After merging the bpf-next tree, today's linux-next build (perf) failed
> > like this:
> >
> > make[3]: *** No rule to make target 'libbpf_util.h', needed by '/home/sfr/next/perf/staticobjs/xsk.o'. Stop.
>
> It's an incremental build issue, as pointed out here [1], that is
> resolved by cleaning the build.
Does this mean there is a deficiency in the dependencies in our build system?
> [1] https://lore.kernel.org/bpf/CAEf4BzYPDF87At4=_gsndxof84OiqyJxgAHL7_jvpuntovUQ8w@mail.gmail.com/
>
> > Caused by commit
> >
> > 7e8bbe24cb8b ("libbpf: xsk: Move barriers from libbpf_util.h to xsk.h")
> >
> > I have used the bpf tree from next-20210310 for today.
I have set my system to remove the object directory before building
after merging the bpf-next tree for now.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists