From: Mark Brown <broonie@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v4.9.95 build: 11 failures 0 warnings (v4.9.95)
Date: Fri, 20 Apr 2018 12:43:55 +0100 [thread overview]
Message-ID: <20180420114355.GA22369@sirena.org.uk> (raw)
In-Reply-To: <20180420064636.GA4009@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]
On Fri, Apr 20, 2018 at 08:46:36AM +0200, Greg KH wrote:
> On Fri, Apr 20, 2018 at 07:41:11AM +0100, Build bot for Mark Brown wrote:
> > Passed: 0 / 11 ( 0.00 %)
> > Failed: 11 / 11 (100.00 %)
> These are "fun" to read :(
This appears to be:
LINK /home/broonie/build/linux-stable/build/tools/objtool/objtool
/home/broonie/build/linux-stable/build/tools/objtool/objtool-in.o: In function `decode_instructions':
/home/broonie/build/linux-stable/tools/objtool/builtin-check.c:296: undefined reference to `arch_decode_instruction'
collect2: error: ld returned 1 exit status
Makefile:45: recipe for target '/home/broonie/build/linux-stable/build/tools/objtool/objtool' failed
make[3]: *** [/home/broonie/build/linux-stable/build/tools/objtool/objtool] Error 1
and then it having problems with build stuff being left in the actual
kernel tree on the rest of the builds causing the build to just refuse
to run (I'm doing out of tree builds). Which is all absolutely
entertaining. This appears to be a combination of something leaving
things in the working tree and then issues cleaning up after a prior
build (I use the same git tree for all stables) so I'm not sure how easy
it's going to be to track down and I need to go get lunch...
I've got the builds doing some extra mrpropers before and after running
builds now to mitigage but clearly there's something wrong somewhere
that's just being papered over.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-04-20 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 6:41 v4.9.95 build: 11 failures 0 warnings (v4.9.95) Build bot for Mark Brown
2018-04-20 6:46 ` Greg KH
2018-04-20 11:43 ` Mark Brown [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=20180420114355.GA22369@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--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).