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 22:00:57 +0000 [thread overview]
Message-ID: <bug-14916-163-Bc68eycUJ4@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14916-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14916
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998@free.fr
--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
(In reply to Thomas Petazzoni from comment #1)
> -GLIBC_CONF_OPTS += --enable-kernel=$(call strip,$(BR2_TOOLCHAIN_HEADERS_AT_LEAST))
> +GLIBC_CONF_OPTS += --enable-kernel=$(call qstrip,$(BR2_TOOLCHAIN_HEADERS_AT_LEAST)).0
It should not be necessary, because the glibc machinery explicitly already adds
a buncha dot-zeroes:
https://github.com/bminor/glibc/blob/master/sysdeps/unix/sysv/linux/configure.ac#L39
(mips has a special case, but uses the same construct).
user_version=$((`echo "$minimum_kernel.0.0.0" | [....]
with minimum_kernel defined there, from --enable-kernel=NNN :
https://github.com/bminor/glibc/blob/master/configure.ac#L273
Note that this is not recent; it's been there since 48d0c5d847a, in 2000...
So yeah, weird...
--
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 22:01 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
2022-07-18 22:00 ` bugzilla [this message]
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-Bc68eycUJ4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.