From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Will Deacon <will.deacon@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Matteo Croce <mcroce@redhat.com>,
Stefano Brivio <sbrivio@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Build/qemu test results for v4.18-rc2
Date: Mon, 25 Jun 2018 09:31:47 -0700 [thread overview]
Message-ID: <20180625163147.GA7112@roeck-us.net> (raw)
In-Reply-To: <CA+55aFzhE2PQOM-pykY=GammunCLYhY37eS_UiYnXWXuSvHLZQ@mail.gmail.com>
On Mon, Jun 25, 2018 at 03:17:47PM +0800, Linus Torvalds wrote:
> On Mon, Jun 25, 2018 at 12:25 AM Guenter Roeck <linux@roeck-us.net> wrote:
> >
> > Build results:
> > total: 134 pass: 113 fail: 21
> > Failed builds:
> > i386:allyesconfig
> > i386:allmodconfig
>
> These seem to be due to the trial code to embed user modules in the
> netfilter modules to use bpf to do netfilter (aka bpfilter). Right
> now that doesn't cross-compile right.
>
Yes, looks like they tried again with c24fb5e68ebf ("bpfilter: fix user
mode helper cross compilation"), but it still doesn't work.
Build reference: v4.18-rc2-37-g6f0d349
gcc version: x86_64-linux-gcc.br_real (Buildroot 2017.02) 6.3.0
Building i386:defconfig ... passed
Building i386:allyesconfig ... failed
x86_64-linux-ld: i386:x86-64 architecture of input file
`net/bpfilter/bpfilter_umh.o' is incompatible with i386 output
Guenter
next prev parent reply other threads:[~2018-06-25 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 16:25 Build/qemu test results for v4.18-rc2 Guenter Roeck
2018-06-25 7:17 ` Linus Torvalds
2018-06-25 8:40 ` Thomas Gleixner
2018-06-25 16:31 ` Guenter Roeck [this message]
2018-06-26 15:40 ` Linus Torvalds
2018-06-27 15:27 ` Linus Torvalds
2018-06-27 16:30 ` Guenter Roeck
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=20180625163147.GA7112@roeck-us.net \
--to=linux@roeck-us.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mcroce@redhat.com \
--cc=sbrivio@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox