On Wed, Aug 22, 2018 at 08:26:58AM -0700, Guenter Roeck wrote:
On Wed, Aug 22, 2018 at 03:07:49PM +0000, Sasha Levin wrote:
On Wed, Aug 22, 2018 at 05:00:39PM +0200, Greg Kroah-Hartman wrote:
On Wed, Aug 22, 2018 at 06:41:50AM -0700, Guenter Roeck wrote:
v4.4.y, v4.9.y:
Building mips:cavium_octeon_defconfig ... failed
Error log:
/opt/buildbot/slave/stable-queue-4.4/build/drivers/net/ethernet/octeon/octeon_mgmt.c: In function 'octeon_mgmt_change_mtu': /opt/buildbot/slave/stable-queue-4.4/build/drivers/net/ethernet/octeon/octeon_mgmt.c:652:6: error: 'size_without_fcs' undeclared
Fixed this now too, thanks.
Sasha, how did this pass your build tests?
greg k-h
Hm, it looks like my mips allmodconfig/allyesconfig were failing with:
req: Cannot open input file certs/x509.genkey, No such file or directory req: Use -help for summary. /home/sasha/data/linux/certs/Makefile:48: recipe for target 'certs/signing_key.pem' failed make[2]: *** [certs/signing_key.pem] Error 1 make[2]: *** Waiting for unfinished jobs....
so that build got blacklister. Guenter, do you see such errors in your builds?
I don't build allyesconfig, but allmodconfig passed. Maybe the build fails only with a more recent version of gcc ? What version of gcc and binutils do you use for your tests ?
Note that you won't see the cavcium build error when building allyesconfig/allmodconfig; that is why I am building it separately.
Apparently when building *some* archs with module signing enabled and using a "O=" external build dir, the build process won't copy over certs/x509.genkey into the build dir and fail.
This doesn't seem to be a new issue, I'm looking into it...