All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Errors when using populate_sdk - has anyone encountered this before?
Date: Thu, 30 Jan 2014 23:03:59 +0100	[thread overview]
Message-ID: <lcei7n$1fo$1@ger.gmane.org> (raw)
In-Reply-To: <CAP71WjxE3bO7f1N9hJtY0JvLnE555z+N+jZ3mrZSWB-k6xSpCw@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nicolas Dechesne schreef op 30-01-14 22:07:
> hi,
> 
> On Thu, Jan 30, 2014 at 10:52 AM, Ridish RA <Ridish.RA@lntinfotech.com>
> wrote:
>> I think I got the root cause of the issue, meta-linaro that we have
>> depends on openembedded-core dylan-qt5.1, but Nicolas recently updated 
>> openembedded-core to dora. And I think this is the root cause of the
>> issue of the relocatable patch being not able to apply?
>> 
>> So do we have meta-linaro layer based openembedded-core dora?
>> 
> 
> yes, the problem is a misalignment between oe-core and meta-linaro. 
> meta-linaro is using a recent qemu upstream commit, and the list of 
> patches from oe-core no longer works with meta-linaro qemu_git recipe. 
> the 2 commits in upstream qemu responsible for the misalignment are:
> 
> 53db78543e473bdf7650a406767d0901c6e26480 
> 964c6fa16f50a607f9da5068d6bf15ccc93872c0
> 
> I am cc'ing riku and koen since that needs fixing in meta-linaro 
> (nativesdk-qemu does not build).
> 
> for now, it's safe to follow Khem's suggestion and use the OE-core qemu.

AUTOREV strikes again :(

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFS6sxPMkyGM64RGpERApmZAJ90opJ7oe/w01M3JeUHmtJIKLYGUgCggfEN
daR9kp8t0Jf/SN0Md1moXxU=
=yKgI
-----END PGP SIGNATURE-----



  reply	other threads:[~2014-01-30 22:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 12:49 [PATCHv2][for-dora] php: update SRC_URI for new download location Chase Maupin
2014-01-30 13:35 ` Errors when using populate_sdk - has anyone encountered this before? Dorairaj, Sanjay
2014-01-30 16:53   ` Khem Raj
     [not found]     ` <EFF5E6A1D0DAA14BA6B30C755A7B0FE13131B2C8EC@BLRINMSMBX01.bglrodc.lntinfotech.com>
2014-01-30 17:59       ` Khem Raj
     [not found]         ` <EFF5E6A1D0DAA14BA6B30C755A7B0FE13131B2C8ED@BLRINMSMBX01.bglrodc.lntinfotech.com>
     [not found]           ` <EFF5E6A1D0DAA14BA6B30C755A7B0FE13131B2C8EF@BLRINMSMBX01.bglrodc.lntinfotech.com>
2014-01-30 21:07             ` Nicolas Dechesne
2014-01-30 22:03               ` Koen Kooi [this message]
2014-01-30 22:07               ` Koen Kooi
2014-01-30 23:12                 ` Dorairaj, Sanjay
2014-01-30 23:22                   ` Ridish Rema Aravindan
2014-01-30 22:42               ` Khem Raj

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='lcei7n$1fo$1@ger.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@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.