Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Olof Johansson <olof.johansson@axis.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/4] qemu: add bash and python to qemu's RDEPENDS
Date: Fri, 22 Nov 2013 12:13:18 +0000	[thread overview]
Message-ID: <1385122398.16887.160.camel@ted> (raw)
In-Reply-To: <20131122083212.GF20888@axis.com>

On Fri, 2013-11-22 at 09:32 +0100, Olof Johansson wrote:
> On 13-11-22 07:25 +0100, Hongxu Jia wrote:
> > Hi Saul,
> > 
> > The script could not be de-bashed,  it was made by create_wrapper
> > which is bashism:
> > Vim image/usr/bin/qemu-mips
> > ...
> > #! /bin/bash
> > realpath=`readlink -fn $0`
> > export QEMU_RESERVED_VA=0x0
> > exec -a `dirname $realpath`/qemu-mips `dirname $realpath`/qemu-mips.real "$@"
> > ...
> > 
> > The exec's -a option is bashism, so we need to add bash to RDEPENDS.
> 
> 1) Is the wrapper still necessary?
> 
> The comment above the do_install_append in the recipe:
> 
> # The following fragment will create a wrapper for qemu-mips user emulation
> # binary in order to work around a segmentation fault issue. Basically, by
> # default, the reserved virtual address space for 32-on-64 bit is set to 4GB.
> # This will trigger a MMU access fault in the virtual CPU. With this change,
> # the qemu-mips works fine.
> # IMPORTANT: This piece needs to be removed once the root cause is fixed!

Someone could retest it but as far as I know the issue still exists.

> 2) More generally, is -a generally necessary when exec'ing like this? Can't
>    this be solved in another way?

We've gone around in circles on this and yes, execing using -a is needed
and if we don't do that we hit other bugs. See the history of the
create_wrapper function.

Cheers,

Richard






      reply	other threads:[~2013-11-22 12:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 13:14 [PATCH 0/4] fix some packages (kconfig-frontends/lttng-tools/lttng-ust/qemu) loss RDEPENDS on python Hongxu Jia
2013-11-21 13:14 ` [PATCH 1/4] kconfig-frontends: add python to kconfig-frontends's RDEPENDS Hongxu Jia
2013-11-21 13:14 ` [PATCH 2/4] lttng-ust: add python to lttng-ust's RDEPENDS Hongxu Jia
2013-11-21 13:14 ` [PATCH 3/4] lttng-tools: add PACKAGECONFIG to support --enable-python-bindings and lttng-ust Hongxu Jia
2013-11-22  6:39   ` Hongxu Jia
2013-11-22 22:30   ` Saul Wold
2013-11-23  1:56     ` Hongxu Jia
2013-11-23  2:02       ` Hongxu Jia
2013-12-05 23:18         ` Saul Wold
2013-11-21 13:14 ` [PATCH 4/4] qemu: add bash and python to qemu's RDEPENDS Hongxu Jia
2013-11-21 18:42   ` Saul Wold
2013-11-21 19:40     ` Mark Hatle
2013-11-21 19:42       ` Saul Wold
2013-11-22  1:52         ` Hongxu Jia
2013-11-22  5:58         ` Hongxu Jia
2013-11-22  6:25           ` Hongxu Jia
2013-11-22  8:32             ` Olof Johansson
2013-11-22 12:13               ` 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=1385122398.16887.160.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=olof.johansson@axis.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