All of lore.kernel.org
 help / color / mirror / Atom feed
From: cli10 <changqing.li@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qemuwrapper-cross: fix postinst failed warning
Date: Thu, 31 May 2018 08:23:20 +0800	[thread overview]
Message-ID: <68f21268-3859-27a4-751a-c67c1274fac0@windriver.com> (raw)
In-Reply-To: <CANNYZj9WjP_FU_SbfZ7OpYqVOrm_HD73vNsY3r9WK4mWn7N4fQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]

On 05/30/2018 06:12 PM, Alexander Kanavin wrote:
> 2018-05-30 12:37 GMT+03:00 cli10 <changqing.li@windriver.com>:
>> if in the future,  some recipe inherit allarch,  but use @qemu_run_binary
>> directly,  not call qemuwrapper,
>>
>> I think maybe still will met problem of get wrong base_libdir. so I think
>> maybe we should change qemu_wrapper_cmdline in
>>
>> qemu.bbclass, like this:
>>
>> -    return "PSEUDO_UNLOAD=1 " + qemu_binary + " " + qemu_options + " -L " +
>> rootfs_path\
>> +    return "PSEUDO_UNLOAD=1 " + "qemuwrapper" + " " + qemu_options + " -L "
>> + rootfs_path\
>>               + " -E LD_LIBRARY_PATH=" + ":".join(library_paths) + " "
> qemu_binary is determined like this:
>
>      qemu_binary = qemu_target_binary(data)
>      if qemu_binary == "qemu-allarch":
>          qemu_binary = "qemuwrapper"
>
> So it will fall back to qemuwrapper if the recipe inherits allarch.
>
> Besides, at this point it's a theoretical problem, right? We don't
> even have a suitable allarch recipe to play with and see where things
> work and where they don't, and whether the fallback to qemuwrapper
> works correctly. If such recipe appears, we can look at the issue
> again.
>
> Alex
>
   yes,  thanks for your comments.

    Changqing

-- 
BRs

Sandy(Li Changqing)
+861084778653


[-- Attachment #2: Type: text/html, Size: 1909 bytes --]

      reply	other threads:[~2018-05-31  0:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30  4:27 [PATCH] qemuwrapper-cross: fix postinst failed warning changqing.li
2018-05-30  6:41 ` Alexander Kanavin
2018-05-30  7:05   ` cli10
2018-05-30  9:37     ` cli10
2018-05-30 10:12       ` Alexander Kanavin
2018-05-31  0:23         ` cli10 [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=68f21268-3859-27a4-751a-c67c1274fac0@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=alex.kanavin@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.