Re: linux-next: build failure after merge of the net-next tree

From: Stephen Rothwell
Date: Wed Jun 06 2018 - 00:49:43 EST


Hi all,

On Fri, 1 Jun 2018 04:52:45 -0400 Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx> wrote:
>
> On Fri, Jun 01, 2018 at 01:59:43PM +1000, Stephen Rothwell wrote:
> >
> > On Thu, 31 May 2018 07:38:55 +1000 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> > >
> > > On Tue, 29 May 2018 13:25:48 +1000 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> > > >
> > > > After merging the net-next tree, today's linux-next build (x86_64
> > > > allmodconfig) failed like this:
> > > >
> > > > x86_64-linux-ld: unknown architecture of input file `net/bpfilter/bpfilter_umh.o' is incompatible with i386:x86-64 output
> > > >
> > > > Caused by commit
> > > >
> > > > d2ba09c17a06 ("net: add skeleton of bpfilter kernel module")
> > > >
> > > > In my builds, the host is PowerPC 64 LE ...
> > > >
> > > > I have reverted that commit along with
> > > >
> > > > 61a552eb487f ("bpfilter: fix build dependency")
> > > > 13405468f49d ("bpfilter: don't pass O_CREAT when opening console for debug")
> > > >
> > > > for today.
> > >
> > > I am still getting this failure (well, at least yesterday I did).
> >
> > Still happened today. My guess is that bpfilter_umh needs to be built
> > with the kernel compiler (not the host compiler - since ir is meant to
> > run on the some machine as the kernel, right?) but will require the
> > kernel architecture libc etc
>
> Sorry for delay. networking folks are traveling to netconf.
> The issue is being discussed here:
> https://patchwork.ozlabs.org/patch/921597/
>
> Currently we're thinking how to add a check that hostcc's arch
> is equal to cross-cc target arch and ideally equal to arch
> of the host where it will be run.

Looks like this is fixed in today's tree by not building bpfilter when
CC cannot link against user libraries. Unfortunately this means that
it will never be built by my infrastructure (since all my compilers are
minimal cross compilers) :-(

I may look into getting a different set of compilers (or doing my
PowerPC builds natively).
--
Cheers,
Stephen Rothwell

Attachment: pgp4F0UWag4wQ.pgp
Description: OpenPGP digital signature