From: Paul Brook <paul@codesourcery.com>
To: "K. Richard Pixley" <rich.pixley@palmsource.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu & arm eabi (armel)
Date: Wed, 27 Sep 2006 19:38:57 +0100 [thread overview]
Message-ID: <200609271938.57898.paul@codesourcery.com> (raw)
In-Reply-To: <451AC2AE.5090902@palmsource.com>
On Wednesday 27 September 2006 19:27, K. Richard Pixley wrote:
> Paul Brook wrote:
> >> Do you know why 2.6.16 would be required? (I'll see if I can't
> >> find/build a 2.6.16 system on which to try it today.)
> >
> > Because arm-linux didn't get EABI support until 2.6.16 (though our
> > toolchains may accept 2.6.14). glibc has santity checks stop applications
> > even trying to run on kernels that are too old.
> >
> > As I mentioned qemu lie about the kernel version. See -r
> > and --enable-uname-release.
>
> I'm confused. My host kernel, (hosted on an x86 ubuntu box), is:
>
> rpixley@svrpixleylnx> uname -r
> 2.6.12-10-686-smp
>
> And my understanding is that there is no kernel when running qemu-user
> because qemu is emulating the kernel calls.
>
> What am I missing? Or where does the kernel version come into play?
glibc startup code checks the kernel version. If the reported version is
earlier than the version it was compiled for it will terminate.
When building glibc you specify a kernel version, and glibc will leave out
backwards compatibility code for older kernels. The runtime check is a sanity
check. It's generally better for the application to die immediately than fail
subtly later on.
Of course when using qemu the syscalls thatqemu emulates tend to be more
important than the host kernel version. By default qemu will report the same
version as the host kernel. However you can tell it to report a different
version.
Paul
next prev parent reply other threads:[~2006-09-27 18:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 21:26 [Qemu-devel] qemu & arm eabi (armel) K. Richard Pixley
2006-09-26 21:36 ` Rafael Espíndola
2006-09-26 21:36 ` Paul Brook
2006-09-26 22:14 ` K. Richard Pixley
2006-09-26 22:30 ` Paul Brook
2006-09-27 17:51 ` K. Richard Pixley
2006-09-27 18:00 ` Paul Brook
2006-09-27 18:27 ` K. Richard Pixley
2006-09-27 18:38 ` Paul Brook [this message]
2006-09-28 3:20 ` Re[2]: " Paul Sokolovsky
2006-09-28 3:39 ` Paul Brook
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=200609271938.57898.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=rich.pixley@palmsource.com \
/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).