From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Holger Hans Peter Freyther <holger@freyther.de>
Cc: poky@yoctoproject.org
Subject: Re: kernel.release being regenerated
Date: Tue, 10 Feb 2015 22:51:26 +0000 [thread overview]
Message-ID: <1423608686.20217.54.camel@linuxfoundation.org> (raw)
In-Reply-To: <20150210184309.GB19902@xiaoyu.lan>
Hi Holger,
On Tue, 2015-02-10 at 19:43 +0100, Holger Hans Peter Freyther wrote:
> I have an integration build that at least builds our sysmocom
> BTS layers against master of Yocto. Our nightly build started
> to be flaky and fail most of the time building the Linux kernel.
>
> We are using a 3.10 LTS kernel for the product and it looks
> like the kernel.release will be (re)created in the build directory
> when the uImage is generated but also when "make modules" is
> called.
>
> This means that shared_workdir in my case should be called at
> a later stage, e.g. after do_compilekernelmodules.
>
> Did anyone else see flaky builds?
We've not see any on the yocto project autobuilders and I've not heard
reports of this from anyone else. I've cc'd Bruce in case he's aware of
anything and can chime in but the new code is being used in many places,
including with 3.10 kernels and I've not heard reports.
The fact the kernel.release is being recreated suggests something in the
configuration is changing (different environment or commandline
options?) or that there is a problem in your kernel to do with the
Makefiles and the dependencies of the kernel.release file.
You might reach a wider audience with questions like this on the yocto
or openembedded-core mailing lists btw, poky tends to be fairly quiet
these days although many of us are here too :)
Cheers,
Richard
next prev parent reply other threads:[~2015-02-10 22:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 18:43 kernel.release being regenerated Holger Hans Peter Freyther
2015-02-10 22:51 ` Richard Purdie [this message]
2015-02-11 4:42 ` Bruce Ashfield
2015-02-11 8:27 ` Holger Hans Peter Freyther
2015-02-11 9:10 ` Richard Purdie
2015-02-11 17:32 ` Bruce Ashfield
2015-02-11 19:35 ` Holger Hans Peter Freyther
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=1423608686.20217.54.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=holger@freyther.de \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.