This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: chroot kernel too old error with glibc 2.24
- From: Carlos O'Donell <carlos at redhat dot com>
- To: RAJESH DASARI <raajeshdasari at gmail dot com>, "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Tue, 10 Jan 2017 01:31:01 -0500
- Subject: Re: chroot kernel too old error with glibc 2.24
- Authentication-results: sourceware.org; auth=none
- References: <CAPXMrf_tdrrXf56oozEi70oW8oEKh=0NaS5QASQNJwqS5i6APQ@mail.gmail.com>
On 01/09/2017 09:49 AM, RAJESH DASARI wrote:
> I am getting the kernel too old error when trying to install the
> 4.4.20 kernel image (with glibc2.24) .
> My machine which is mips based and has 2.6.34 kernel installed , i am
> trying to install the new kernel(4.4.20) which has 2.24 glibc version
>
> 1 . I mounted the latest kernel image on /mnt/latest
> 2. Executed chroot to that image path
> # chroot /mnt/latest
> FATAL: kernel too old
>
> I see that in 2.24 release notes, it is mentioned that the minimum
> Linux kernel version that this version of the GNU C Library can be
> used with is 3.2.
>
> I am sure this is not a bug in glibc , but could some one help me how
> to get rid of this problem ,
> I have compiled glibc with --enable-kernel=2.6.32 option but still no help.
To use glibc 2.24 you must first boot with a kernel > 3.2 e.g. your 4.4.20 kernel.
You cannot configure glibc 2.24 to run with a 2.6.32 kernel.
I have moved this conversation to libc-help.
Cheers,
Carlos.