From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, james@alentdesignsolutions.com
Subject: Re: [Qemu-devel] chroot to ARM Gentoo install.
Date: Tue, 24 Aug 2004 21:06:57 +0100 [thread overview]
Message-ID: <200408242106.57803.paul@codesourcery.com> (raw)
In-Reply-To: <200408241238.32517.james@alentdesignsolutions.com>
On Tuesday 24 August 2004 20:38, James Pellow wrote:
> Hi All,
>
> Thanks for a truely awesome tool! I have some custom ARM hardware that I
> have ported the linux kernel to, and for fun I want to install Gentoo on
> it. Since gentoo requires a fair piece of compiling (gasp...) and since my
> board only runs at 74MHz, I thought I would try chroot'ing into ARM gentoo
> using qemu on my Athlon system. (Yes, I have tried distcc... Its still
> slow.) I have been able to set up binfmt_misc and a statically compiled
> qemu-arm to chroot into an arm busybox install (uClibc), but for some
> reason I get the following error when I try to chroot into a gentoo root
> (full glibc):
You might see if the this patch helps:
http://lists.gnu.org/archive/html/qemu-devel/2004-08/msg00015.html
You don't mention what sort of ARM chip you are using. qemu only supports
armv4. It does not currently implement the armv4t or armv5 instruction sets.
I have patches implementing armv5te, but they still need testing.
Paul
next prev parent reply other threads:[~2004-08-24 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 19:38 [Qemu-devel] chroot to ARM Gentoo install James Pellow
2004-08-24 20:06 ` Paul Brook [this message]
2004-08-24 21:26 ` Lennert Buytenhek
2004-08-24 21:44 ` Paul Brook
2004-08-24 22:14 ` Fabrice Bellard
2004-08-24 22:26 ` Paul Brook
2004-08-25 22:36 ` Fabrice Bellard
2004-08-26 23:48 ` Paul Brook
2004-12-18 21:18 ` Lennert Buytenhek
2004-08-24 22:44 ` James Pellow
2004-08-24 22:44 ` 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=200408242106.57803.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=james@alentdesignsolutions.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).