public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kernel-devsrc: Handle ppc crtsaves.o explictly for now
Date: Mon, 22 Dec 2014 09:09:18 +0000	[thread overview]
Message-ID: <1419239358.13316.65.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4OYpdJYGjb7DB6a7kEUiCP=zUjLahddNJjy5CjxM8VqFg@mail.gmail.com>

On Sun, 2014-12-21 at 23:43 -0400, Bruce Ashfield wrote:
> On Sun, Dec 21, 2014 at 8:29 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Resolve kernel module build failures for qemuppc by including crtsaves.o.
> >
> > I'm not particularly happy to be doing this, it should perhaps be contained
> > in the kernel-dev package. Until the overlap between kernel-devsrc and
> > kernel-dev is resolved, this at least removed the regressions.
> 
> Interesting. I built qemuppc for core-image-kerneldev and core-image-sato and
> didn't see this.
> 
> Are the build steps that triggered this captured in the bug ? Or are they in the
> mailing list thread ? Either way, I'd like to run them here as part of
> any follow
> on cleanups.
> 
> But the patch makes sense, and looks fine to me for the current state.

Reproducer is/was in local.conf:

TEST_IMAGE = "1"
TEST_SUITES = "kernelmodule"

MACHINE=qemuppc bitbake core-image-sato-sdk

which will then build the image, boot it and then try and build a kernel
module. I did cheat and disable QT4 when I did it locally.

Cheers,

Richard




      reply	other threads:[~2014-12-22  9:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21 12:29 [PATCH] kernel-devsrc: Handle ppc crtsaves.o explictly for now Richard Purdie
2014-12-22  3:43 ` Bruce Ashfield
2014-12-22  9:09   ` Richard Purdie [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=1419239358.13316.65.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox