On 05/30/2018 06:12 PM, Alexander Kanavin wrote:
2018-05-30 12:37 GMT+03:00 cli10 :
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_wr
2018-05-30 12:37 GMT+03:00 cli10 :
> 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 thi
Hi, Alex
I have test with your patch, test passed, all warnings are fixed:-).
But I have a problem about this, could you help to give some comments?
Thanks.
if in the future, some recipe inherit allarch, but use
@qemu_run_binary directly, not call qemuwrapper,
I think maybe still wi
OK, I will test with your patch:-)
On 05/30/2018 02:41 PM, Alexander Kanavin wrote:
2018-05-30 7:27 GMT+03:00 :
From: Changqing Li
1. some binary like udev-hwdb/pixbufcache/gio-module-cache/fontcache
uses qemu usermode by default, but some architecture such as Intel
skylake does not support
2018-05-30 7:27 GMT+03:00 :
> From: Changqing Li
>
> 1. some binary like udev-hwdb/pixbufcache/gio-module-cache/fontcache
> uses qemu usermode by default, but some architecture such as Intel
> skylake does not support qemu usermode, this can lead to a build warning as
> below:
> 2. font is not
From: Changqing Li
1. some binary like udev-hwdb/pixbufcache/gio-module-cache/fontcache
uses qemu usermode by default, but some architecture such as Intel
skylake does not support qemu usermode, this can lead to a build warning as
below:
warning: %post(udev-hwdb-1:234-r0.skylake_64) scriptlet f
