From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [v2 PATCH 0/9] kernel: version updates
Date: Thu, 11 Dec 2014 13:58:44 +0000 [thread overview]
Message-ID: <1418306324.22903.72.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4P0XMtSxKop9vqr6SbS8KBmaGuZfKFs7Ej0CsDcqLt4DQ@mail.gmail.com>
On Thu, 2014-12-11 at 03:31 -0500, Bruce Ashfield wrote:
> On Wed, Dec 10, 2014 at 10:02 AM, Burton, Ross <ross.burton@intel.com> wrote:
> >
> > On 10 December 2014 at 14:16, Bruce Ashfield <bruce.ashfield@windriver.com>
> > wrote:
> >>
> >> The following changes since commit
> >> 88dfcbf149dda89277e58ae4ec3a87500624cfff:
> >>
> >> kernel-yocto: make sure git tags get dereferenced properly in do_patch()
> >> (2014-12-10 08:12:56 -0500)
> >>
> >> are available in the git repository at:
> >>
> >> git://git.pokylinux.org/poky-contrib HEAD
> >
> >
> > I wonder what happened here!
>
> @#!$#@$ the script is insane.
>
> >
> >>
> >> for you to fetch changes up to 4be985be419f06f18c735d72ac4a4d00fea71dd8:
> >>
> >> linux-yocto/3.14: update to 3.14.26, integrate ltsi and -rt updates
> >> (2014-12-10 08:38:49 -0500)
> >
> >
> > That's zedd/kernel-updates, right?
> >
>
> Yah. Sorry about the confusion,
I've been experimenting, the upgrades look good but we have a problem
with the new kernel class changes.
The issue is that if you have an existing TMPDIR, the build will do "bad
things".
Basically, there is usually an existing sstate manifest file which
covers the kernel source in the sysroot. do_configure will trigger
cleaning of that manifest, a large chunk of the source disappears and
then the build understandably fails.
Whilst I can say what is happening, I can't say how we fix it at this
point :/.
I would like people to test these patches, we'd better hold off merging
until we can get this issue figured out. Its part of a wider problem
with "stale" data in the sysroot which we really need to figure out but
its not been solved yet as its a very hard problem for which we don't
have a solution :(.
Cheers,
Richard
next prev parent reply other threads:[~2014-12-11 13:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 14:16 [v2 PATCH 0/9] kernel: version updates Bruce Ashfield
2014-12-10 14:16 ` [PATCH 1/9] linux-yocto/3.17: update to v3.17.1 Bruce Ashfield
2014-12-10 14:16 ` [PATCH 2/9] linux-libc-headers: update to 3.17 Bruce Ashfield
2014-12-18 17:13 ` Burton, Ross
2014-12-18 17:39 ` Bruce Ashfield
2014-12-18 18:41 ` Bruce Ashfield
2014-12-18 20:46 ` Burton, Ross
2014-12-18 23:48 ` Burton, Ross
2014-12-10 14:16 ` [PATCH 3/9] linux-yocto/3.17: update to v3.17.2 Bruce Ashfield
2014-12-10 14:16 ` [PATCH 4/9] linux-yocto/3.10: update to v3.10.59 Bruce Ashfield
2014-12-10 14:16 ` [PATCH 5/9] linux-yocto/3.14: update to v3.14.24 Bruce Ashfield
2014-12-10 14:16 ` [PATCH 6/9] lttng-modules: fix mm_compaction_isolate_template build Bruce Ashfield
2014-12-10 14:16 ` [PATCH 7/9] linux-yocto/3.17: update to v3.17.6 Bruce Ashfield
2014-12-10 14:16 ` [PATCH 8/9] linux-yocto/3.10: update to v3.10.62 Bruce Ashfield
2014-12-10 14:16 ` [PATCH 9/9] linux-yocto/3.14: update to 3.14.26, integrate ltsi and -rt updates Bruce Ashfield
2014-12-10 15:02 ` [v2 PATCH 0/9] kernel: version updates Burton, Ross
2014-12-11 8:31 ` Bruce Ashfield
2014-12-11 13:58 ` Richard Purdie [this message]
2014-12-11 14:56 ` Richard Purdie
2014-12-11 15:26 ` Bruce Ashfield
2014-12-11 15:35 ` Burton, Ross
2014-12-11 21:21 ` Bruce Ashfield
2014-12-11 16:45 ` Tom Zanussi
2014-12-11 19:54 ` Tom Zanussi
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=1418306324.22903.72.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.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.