<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 2017年12月28日 15:50, Martin Jansa
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+chaQdBwU7HjBwtwMoyWjZYgQTmyM3n6q_2KpLWLNMsieYYhg@mail.gmail.com">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">> <span>No,some MACHINEs not support qemu
usermode</span>
<div><span><br>
</span></div>
<div><span>That's not what I was asking.</span></div>
<div><span><br>
</span></div>
<div><span>You're disabling whole build-time postinst when
qemu-usermode is in MACHINE_FEATURES with:</span></div>
<div><span>${@bb.utils.contains('MACHINE_</span><wbr><span>FEATURES',
'qemu-usermode', 'true','false', d)}</span><span><br>
</span></div>
<div><span><br>
</span></div>
<div><span>and in that case read-only images will fail to build
and even if you remove that error (failed postinst scripts
are causing errors when the image is configured to be
read-only), then the image is still bad for runtime, because
with read-only rootfs you cannot generate fontcache even on
the device.</span></div>
<div><span><br>
</span></div>
</div>
</blockquote>
Yes, If the <span class="">MACHINE not support </span><span>qemu-usermode,
</span><span><span class="">postinst can not be executed on
read-only rootfs. <br>
<br>
but I think this is a common issue. postinstall used qemu
usermode directly without any check, it will fail on unsupported
machine </span></span><span><span class=""><span><span class="">certainly.<br>
but </span></span>I think we should check </span></span><span><span
class="">whether support </span></span><span><span class="">qemu
usermode, and if not ,tell the caller.<br>
</span> <br>
thanks,<br>
Jibin<br>
<br>
</span><span></span>
<blockquote type="cite"
cite="mid:CA+chaQdBwU7HjBwtwMoyWjZYgQTmyM3n6q_2KpLWLNMsieYYhg@mail.gmail.com">
<div class="gmail_extra">
<div class="gmail_quote">On Thu, Dec 28, 2017 at 8:42 AM, Jibin
Xu <span dir="ltr"><<a
href="mailto:jibin.xu@windriver.com" target="_blank"
moz-do-not-send="true">jibin.xu@windriver.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote">
<div>
<p>I will send a right one for the typos.</p>
<span class="">
<p>"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?"</p>
</span>
<p>No,some MACHINEs not support qemu usermode, when used,
it will lead to a qemu core dump: "qemu: uncaught target
signal 11 (Segmentation fault) - core dumped".</p>
<p>so when use qemu usermode,check whether the machine
supports it first. <br>
</p>
<p>Thanks,</p>
<p>Jibin<br>
</p>
<div>
<div class="h5">
<div class="m_5674333459630589526moz-cite-prefix">On
2017年12月28日 15:11, Martin Jansa wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">There are 2 typos in "qemu".
<div><br>
</div>
<div>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?</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Dec 28, 2017 at
3:21 AM, Jibin Xu <span dir="ltr"><<a
href="mailto:jibin.xu@windriver.com"
target="_blank" moz-do-not-send="true">jibin.xu@windriver.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote">fontcache uses
quemu usermode by default, but some
architecture<br>
such as Intel skylake does not support qemu
usermode, this can<br>
lead to a build warning as below:<br>
"WARNING: The postinstall intercept hook
'update_font_cache' failed".<br>
<br>
Add a judgement of qemu usermode to fix the
build warning.<br>
<br>
Signed-off-by: Jibin Xu <<a
href="mailto:jibin.xu@windriver.com"
target="_blank" moz-do-not-send="true">jibin.xu@windriver.com</a>><br>
---<br>
meta/classes/fontcache.<wbr>bbclass | 18
+++++++++++-------<br>
1 file changed, 11 insertions(+), 7
deletions(-)<br>
<br>
diff --git a/meta/classes/fontcache.bbcla<wbr>ss
b/meta/classes/fontcache.bbcla<wbr>ss<br>
index e76331131e..3eb868fa08 100644<br>
--- a/meta/classes/fontcache.bbcla<wbr>ss<br>
+++ b/meta/classes/fontcache.bbcla<wbr>ss<br>
@@ -17,13 +17,17 @@ FONTCONFIG_CACHE_PARAMS ?=
"-v"<br>
FONTCONFIG_CACHE_ENV ?= "FC_DEBUG=1"<br>
fontcache_common() {<br>
if [ -n "$D" ] ; then<br>
- $INTERCEPT_DIR/postinst_inter<wbr>cept
update_font_cache ${PKG} mlprefix=${MLPREFIX}
\<br>
- 'bindir="${bindir}"' \<br>
- 'libdir="${libdir}"' \<br>
- 'base_libdir="${base_libdir}"<wbr>'
\<br>
- 'fontconfigcachedir="${FONTCO<wbr>NFIG_CACHE_DIR}"'
\<br>
- 'fontconfigcacheparams="${FON<wbr>TCONFIG_CACHE_PARAMS}"'
\<br>
- 'fontconfigcacheenv="${FONTCO<wbr>NFIG_CACHE_ENV}"'<br>
+ if ${@bb.utils.contains('MACHINE_<wbr>FEATURES',
'qemu-usermode', 'true','false', d)}; then<br>
+ $INTERCEPT_DIR/postinst_inter<wbr>cept
update_font_cache ${PKG} mlprefix=${MLPREFIX}
\<br>
+ 'bindir="${bindir}"' \<br>
+ 'libdir="${libdir}"' \<br>
+
'base_libdir="${base_libdir}"<wbr>' \<br>
+
'fontconfigcachedir="${FONTCO<wbr>NFIG_CACHE_DIR}"'
\<br>
+
'fontconfigcacheparams="${FON<wbr>TCONFIG_CACHE_PARAMS}"'
\<br>
+
'fontconfigcacheenv="${FONTCO<wbr>NFIG_CACHE_ENV}"'<br>
+ else<br>
+ exit 1<br>
+ fi<br>
else<br>
${FONTCONFIG_CACHE_ENV} fc-cache
${FONTCONFIG_CACHE_PARAMS}<br>
fi<br>
<span class="m_5674333459630589526HOEnZb">--<br>
2.13.0<br>
<br>
--<br>
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a
href="mailto:Openembedded-core@lists.openembedded.org"
target="_blank" moz-do-not-send="true">Openembedded-core@lists.openem<wbr>bedded.org</a><br>
<a
href="http://lists.openembedded.org/mailman/listinfo/openembedded-core"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</span></blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>