Re: [OE-core] [PATCH] fontcache : fix build warning when using quemu usermode

2018-01-03 Thread Alexander Kanavin
On 01/03/2018 05:27 AM, Jibin Xu wrote: On 2018年01月02日 20:00, Alexander Kanavin wrote: On 12/28/2017 04:21 AM, Jibin Xu wrote: fontcache uses quemu usermode by default, but some architecture such as Intel skylake does not support qemu usermode, this can lead to a build warning as below: "WARN

Re: [OE-core] [PATCH] fontcache : fix build warning when using quemu usermode

2018-01-02 Thread Jibin Xu
On 2018年01月02日 20:00, Alexander Kanavin wrote: On 12/28/2017 04:21 AM, Jibin Xu wrote: fontcache uses quemu 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: The postinstall intercept hook 'upda

Re: [OE-core] [PATCH] fontcache : fix build warning when using quemu usermode

2018-01-02 Thread Alexander Kanavin
On 12/28/2017 04:21 AM, Jibin Xu wrote: fontcache uses quemu 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: The postinstall intercept hook 'update_font_cache' failed". Add a judgement of qemu u

Re: [OE-core] [PATCH] fontcache : fix build warning when using quemu usermode

2017-12-28 Thread Jibin Xu
On 2017年12月28日 15:50, Martin Jansa wrote: > No,some MACHINEs not support qemu usermode That's not what I was asking. You're disabling whole build-time postinst when qemu-usermode is in MACHINE_FEATURES with: ${@bb.utils.contains('MACHINE_FEATURES', 'qemu-usermode', 'true','false', d)} and

Re: [OE-core] [PATCH] fontcache : fix build warning when using quemu usermode

2017-12-28 Thread Zhixiong Chi
On 2017年12月28日 15:50, Martin Jansa wrote: > No,some MACHINEs not support qemu usermode That's not what I was asking. You're disabling whole build-time postinst when qemu-usermode is in MACHINE_FEATURES with: ${@bb.utils.contains('MACHINE_FEATURES', 'qemu-usermode', 'true','false', d)} Hi,

Re: [OE-core] [PATCH] fontcache : fix build warning when using quemu usermode

2017-12-27 Thread Martin Jansa
> No,some MACHINEs not support qemu usermode That's not what I was asking. You're disabling whole build-time postinst when qemu-usermode is in MACHINE_FEATURES with: ${@bb.utils.contains('MACHINE_FEATURES', 'qemu-usermode', 'true','false', d)} and in that case read-only images will fail to build

Re: [OE-core] [PATCH] fontcache : fix build warning when using quemu usermode

2017-12-27 Thread Jibin Xu
I will send a right one for the typos. "Does this mean that MACHINEs which use qemu usermode won't be able to use read-only images where this postinst cannot be executed on read-only rootfs?" No,some MACHINEs not support qemu usermode, when used, it will lead to a qemu core dump: "qemu: unca

Re: [OE-core] [PATCH] fontcache : fix build warning when using quemu usermode

2017-12-27 Thread Martin Jansa
There are 2 typos in "qemu". Does this mean that MACHINEs which use qemu usermode won't be able to use read-only images where this postinst cannot be executed on read-only rootfs? On Thu, Dec 28, 2017 at 3:21 AM, Jibin Xu wrote: > fontcache uses quemu usermode by default, but some architecture

[OE-core] [PATCH] fontcache : fix build warning when using quemu usermode

2017-12-27 Thread Jibin Xu
fontcache uses quemu 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: The postinstall intercept hook 'update_font_cache' failed". Add a judgement of qemu usermode to fix the build warning. Signed-