From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14916] build buildroot with glibc and linux kernel 5.4, start with qemu will cause error: "FATAL: kernel too old"
Date: Mon, 18 Jul 2022 21:43:10 +0000 [thread overview]
Message-ID: <bug-14916-163-qp3mLkzsUX@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14916-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14916
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
Thanks for the bug report. I am surprised we never realized this before.
Isn't the solution as simple as:
diff --git a/package/glibc/glibc.mk b/package/glibc/glibc.mk
index f3a08fbf24..6c54d044a5 100644
--- a/package/glibc/glibc.mk
+++ b/package/glibc/glibc.mk
@@ -99,7 +99,7 @@ GLIBC_MAKE = $(BR2_MAKE)
GLIBC_CONF_ENV += ac_cv_prog_MAKE="$(BR2_MAKE)"
ifeq ($(BR2_PACKAGE_GLIBC_KERNEL_COMPAT),)
-GLIBC_CONF_OPTS += --enable-kernel=$(call
qstrip,$(BR2_TOOLCHAIN_HEADERS_AT_LEAST))
+GLIBC_CONF_OPTS += --enable-kernel=$(call
qstrip,$(BR2_TOOLCHAIN_HEADERS_AT_LEAST)).0
endif
# Even though we use the autotools-package infrastructure, we have to
Indeed, $(BR2_TOOLCHAIN_HEADERS_AT_LEAST) never includes the minor version as
far as I can see. Yann, any opinion?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-18 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 2:43 [Buildroot] [Bug 14916] New: build buildroot with glibc and linux kernel 5.4 will cause error: "FATAL: kernel too old" bugzilla
2022-07-18 2:46 ` [Buildroot] [Bug 14916] build buildroot with glibc and linux kernel 5.4, start with qemu " bugzilla
2022-07-18 6:25 ` bugzilla
2022-07-18 21:43 ` bugzilla [this message]
2022-07-18 22:00 ` bugzilla
2022-07-19 3:27 ` bugzilla
2022-07-23 14:05 ` bugzilla
2022-10-25 20:22 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-14916-163-qp3mLkzsUX@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox