qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Rigby <john.rigby@linaro.org>
To: qemu-devel@nongnu.org
Cc: 'Peter Maydell <peter.maydell@linaro.org>,
	John Rigby <john.rigby@linaro.org>,
	Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] [PATCH v3 resend 11/11] linux-user: AArch64 requires at least 3.8.0
Date: Mon, 13 May 2013 00:57:58 -0600	[thread overview]
Message-ID: <1368428278-29299-12-git-send-email-john.rigby@linaro.org> (raw)
In-Reply-To: <1368428278-29299-1-git-send-email-john.rigby@linaro.org>

From: Alexander Graf <agraf@suse.de>

Glibc 1.17 checks for the host kernel version on startup. Unfortunately,
it also checks whether the host kernel version is recent enough for the
target to run at all.

Since AArch64 support only got introduced in 3.8.0, that means that glibc
refuses to run on any older kernel version than that.

To allow for execution of linux-user guests even on older host kernels,
let's always fake the kernel version to 3.8.0 on AArch64 guests.

Do this by forcing CONFIG_UNAME_RELEASE=3.8.0 in config_target_mak
for aarch64.

Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: John Rigby <john.rigby@linaro.org>
---

Changes in v2:
- Move patch to last in series and implement by forcing
  CONFIG_UNAME_RELEASE=3.8.0 in config_target_mak

 configure | 1 +
 1 file changed, 1 insertion(+)

diff --git a/configure b/configure
index 4f5be7a..5f9eb57 100755
--- a/configure
+++ b/configure
@@ -4198,6 +4198,7 @@ case "$target_arch2" in
     target_nptl="yes"
     gdb_xml_files="aarch64-core.xml aarch64-fpu.xml"
     target_long_alignment=8
+    echo "CONFIG_UNAME_RELEASE=\"3.8.0\"" >> $config_target_mak
   ;;
   cris)
     target_nptl="yes"
-- 
1.8.2.2

  parent reply	other threads:[~2013-05-13  6:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13  6:57 [Qemu-devel] [PATCH v3 resend 00/11] AArch64 preparation patch set John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 01/11] ARM: Export cpu_env John Rigby
2013-05-13  9:28   ` Peter Maydell
2013-05-13 10:07     ` Alexander Graf
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 02/11] ARM: Prepare translation for AArch64 code John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 03/11] ARM: Add AArch64 translation stub John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 04/11] AArch64: Add gdb stub John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 05/11] linux-user: Don't treat aarch64 cpu names specially John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 06/11] linux-user: Add syscall handling for AArch64 John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 07/11] linux-user: Fix up AArch64 syscall handlers John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 08/11] linux-user: Add signal handling for AArch64 John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 09/11] linux-user: Add AArch64 support John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 10/11] ARM: Add aarch64 target to configure John Rigby
2013-05-13  6:57 ` John Rigby [this message]
2013-05-13  8:54 ` [Qemu-devel] [PATCH v3 resend 00/11] AArch64 preparation patch set Peter Maydell
2013-05-13 13:40   ` John Rigby

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=1368428278-29299-12-git-send-email-john.rigby@linaro.org \
    --to=john.rigby@linaro.org \
    --cc=agraf@suse.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).