qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2 2/5] linux-user: Add separate aarch64_be unam


From: Michael Weiser
Subject: Re: [Qemu-devel] [PATCH v2 2/5] linux-user: Add separate aarch64_be uname
Date: Wed, 20 Dec 2017 17:01:06 +0100
User-agent: Mutt/1.9.1 (2017-09-22)

Hi Peter,

On Wed, Dec 20, 2017 at 03:36:29PM +0000, Peter Maydell wrote:

> >>  #define UNAME_MINIMUM_RELEASE "3.8.0"

> > For aarch64_be, I think the minimum release should be 4.9.0
> > (see kernel commit cfa88c79462d "arm64: Set UTS_MACHINE in the Makefile")

> Isn't the thing that defines what we set the minimum-release
> to glibc, not the kernel? That is, the reason we lie to the
> guest about the kernel version for some architectures is because
> the glibc for those archs insists on a minimum kernel version
> which the host may not have. Unless aarch64_be glibc insists
> on kernel 4.9.0 there's no need to tell the guest that.

I can confirm that cross-compiled glibc runs fine with the current
value. Also, a native compile of glibc inside an qemu-aarch64_be binfmt
chroot configured without problem and currently churns along compiling.

My Gentoo setup calls configure with --enable-kernel=3.2.0 and that says
about this:

checking installed Linux kernel header files... 3.2.0 or later
configure: WARNING: minimum kernel version reset to 3.7.0
checking for kernel header at least 3.7.0... ok

So it seems your memory is right.
-- 
Bye,
Michael



reply via email to

[Prev in Thread] Current Thread [Next in Thread]