summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/glibc/glibc.inc
diff options
context:
space:
mode:
authorHe Zhe <zhe.he@windriver.com>2021-02-26 22:20:45 +0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-03-02 14:15:34 +0000
commit3f7a2ca81bb68495bf47ceb8f47ebd8f555d545f (patch)
tree8a58053d78f2151b767b915f7ea3c8ce7df1046f /meta/recipes-core/glibc/glibc.inc
parentb81b46ea4877a79853e66faf4b49ff2588cbb2fb (diff)
downloadpoky-3f7a2ca81bb68495bf47ceb8f47ebd8f555d545f.tar.gz
glibc: Disable CPU ISA level requirement check
We experience the following error and fail to boot on qemu64 machine /lib64/libc.so.6: CPU ISA level is lower than required Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 As stated in [1], Passing -march= causes glibc to add annotations not compatible to run result on -march= as too high ISA level is inferred. ISA level is a new feature of 2.33 release. Until it's fixed let's disable ISA level inference with libc_cv_include_x86_isa_level=no (no better configure option yet). [1] https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5dbd6a821ff753e3b41324c4fb7c58cf65eeea33 (From OE-Core rev: 91264e14a088013b138e82520744f79fa7c8d585) Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/glibc/glibc.inc')
-rw-r--r--meta/recipes-core/glibc/glibc.inc1
1 files changed, 1 insertions, 0 deletions
diff --git a/meta/recipes-core/glibc/glibc.inc b/meta/recipes-core/glibc/glibc.inc
index d2f02ad59b..7d14306377 100644
--- a/meta/recipes-core/glibc/glibc.inc
+++ b/meta/recipes-core/glibc/glibc.inc
@@ -20,6 +20,7 @@ CACHED_CONFIGUREVARS += " \
20 libc_cv_ssp_strong=no \ 20 libc_cv_ssp_strong=no \
21 libc_cv_ssp_all=no \ 21 libc_cv_ssp_all=no \
22 libc_cv_ssp=no \ 22 libc_cv_ssp=no \
23 libc_cv_include_x86_isa_level=no \
23" 24"
24 25
25# ifunc doesn't appear to work on mips, casuses libbfd assertion failures 26# ifunc doesn't appear to work on mips, casuses libbfd assertion failures