Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Chris Patterson <cjp256@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qemu: upgrade to 1.6.1
Date: Tue, 29 Oct 2013 09:27:30 +0200	[thread overview]
Message-ID: <20131029072729.GB6291@lpalcu-linux> (raw)
In-Reply-To: <CABZSBQepb=+J-OSGkD7Kt-u9sZU0eLJ+-NSqZS-np9tp6xc2RQ@mail.gmail.com>

Hi Chris,

On Mon, Oct 28, 2013 at 07:54:51PM -0400, Chris Patterson wrote:
> 
> I'm not terribly familiar with the nativesdk, and (foolishly) neglected to test
> that.  However, I looked into it, and it looks like the relocatable_sdk.patch
> affects a linker script that is no longer available.  I dropped the patch and
> tested installing an oe-core sdk sysroot (via bitbake -c populate_sdk
> core-image-minimal) and qemu appears to work fine from within the sdk
> environment.
> 
> I'm open to suggestions for further testing this upgrade (particularly a case
> to cover what relocatable_sdk.patch was originally intended to resolve). I'm
> certainly not the expert here, but am willing to help out.
> 
To test this particular case, build meta-toolchain and install it in a
different location than the default one. Then, just do a 'readelf -s"
on any qemu binary and make sure the .interp section has a size of 0x1000 bytes.

If it does, then it's ok to drop the patch. That patch was needed
because qemu happened to use their own linker scripts and, in order to
have the SDK relocatable, we needed to reseve space in the .interp
section to squeeze the new path.

Laurentiu


  reply	other threads:[~2013-10-29  7:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16  0:15 [PATCH] qemu: upgrade to 1.6.1 Chris Patterson
2013-10-24  8:48 ` Saul Wold
2013-10-28 23:54   ` Chris Patterson
2013-10-29  7:27     ` Laurentiu Palcu [this message]
2013-10-29 20:20       ` Chris Patterson
2013-10-29 20:30         ` Saul Wold
2013-10-30 11:49           ` Chris Patterson

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=20131029072729.GB6291@lpalcu-linux \
    --to=laurentiu.palcu@intel.com \
    --cc=cjp256@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