From: Sasha Levin <Alexander.Levin@microsoft.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable <stable@vger.kernel.org>
Subject: Re: Build failures in -stable queues
Date: Wed, 22 Aug 2018 17:51:25 +0000 [thread overview]
Message-ID: <20180822175124.GD2193@sasha-vm> (raw)
In-Reply-To: <20180822152658.GA10136@roeck-us.net>
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...
prev parent reply other threads:[~2018-08-22 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 13:41 Build failures in -stable queues Guenter Roeck
2018-08-22 14:56 ` Greg Kroah-Hartman
2018-08-22 15:05 ` Sasha Levin
2018-08-22 15:00 ` Greg Kroah-Hartman
2018-08-22 15:07 ` Sasha Levin
2018-08-22 15:26 ` Guenter Roeck
2018-08-22 17:51 ` Sasha Levin [this message]
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=20180822175124.GD2193@sasha-vm \
--to=alexander.levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).