qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "K. Richard Pixley" <rich.pixley@palmsource.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu & arm eabi (armel)
Date: Wed, 27 Sep 2006 11:27:58 -0700	[thread overview]
Message-ID: <451AC2AE.5090902@palmsource.com> (raw)
In-Reply-To: <200609271900.45440.paul@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

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?

--rich

[-- Attachment #2: Type: text/html, Size: 1183 bytes --]

  reply	other threads:[~2006-09-27 18:28 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 [this message]
2006-09-27 18:38             ` Paul Brook
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=451AC2AE.5090902@palmsource.com \
    --to=rich.pixley@palmsource.com \
    --cc=paul@codesourcery.com \
    --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).