On qemumips64, `systemctl status <unit>' would have the output of `systemctl show <unit>'. This is incorrect.
However, it's not the code logic that cause such problem. It's the compilation flags. Looking back the history, we had problem with systemd on qemumips64 which is also related to compilation flags. We solved that by using tweaking FULL_OPTIMIZATION for mips64 to have "-fno-tree-switch-conversion -fno-tree-tail-merge". Now systemd has been upgraded to 234, and we don't have the above problem any more. However, a new problem appears, and that is the output of `systemctl status <unit>'. Hence, we set '-O0' flag for mips64 when building systemd to avoid potential strange problems. [YOCTO #12266] Signed-off-by: Chen Qi <[email protected]> --- meta/recipes-core/systemd/systemd_234.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-core/systemd/systemd_234.bb b/meta/recipes-core/systemd/systemd_234.bb index 36fd3f8..b294604 100644 --- a/meta/recipes-core/systemd/systemd_234.bb +++ b/meta/recipes-core/systemd/systemd_234.bb @@ -158,8 +158,8 @@ CFLAGS .= "${@bb.utils.contains('PACKAGECONFIG', 'valgrind', ' -DVALGRIND=1', '' # disable problematic GCC 5.2 optimizations [YOCTO #8291] FULL_OPTIMIZATION_append_arm = " -fno-schedule-insns -fno-schedule-insns2" -# Avoid login failure on qemumips64 when pam is enabled -FULL_OPTIMIZATION_append_mips64 = " -fno-tree-switch-conversion -fno-tree-tail-merge" +# Disable optimization on qemumips64 to avoid strange behaviour +FULL_OPTIMIZATION_append_mips64 = " -O0" COMPILER_NM ?= "${HOST_PREFIX}gcc-nm" COMPILER_AR ?= "${HOST_PREFIX}gcc-ar" -- 1.9.1 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
