From: James Pellow <james@alentdesignsolutions.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] chroot to ARM Gentoo install.
Date: Tue, 24 Aug 2004 15:44:59 -0700 [thread overview]
Message-ID: <200408241544.59356.james@alentdesignsolutions.com> (raw)
In-Reply-To: <200408242106.57803.paul@codesourcery.com>
On Tuesday 24 August 2004 01:06 pm, Paul Brook wrote:
> 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
Hi Paul,
Thanks for the quick reply. I am using an armv4 chip, specifically an
arm720tdmi. All code has been built for armv4.
I tried the patch you pointed me to. Unfortunately I am still seeing the same
results as previously noted. Looking at the source for ld.so, I note that
this is all happening in the elf parsing code. The actual assert looks like:
assert (info[DT_PLTREL]->d_un.d_val == DT_REL
|| info[DT_PLTREL]->d_un.d_val == DT_RELA);
(elf/dynamic-link.h:126)
for the case where !ELF_MACHINE_NO_RELA && !ELF_MACHINE_NO_REL are not
defined... That didn't make much sense to me yet, as I haven't poked around
in glibc much. Its hard for me to imagine that the problem is in glibc
though since it shouldn't know the difference between running natively and
running under qemu. (Or is there a subtle difference?) It more obviously
seems like elf should parse same either in emulation or not. Since qemu
doesn't signal, how should I procede in debugging this? Any further ideas?
Thanks for your help.
Regards,
--
----------------------------
James Pellow, President
Alent Design Solutions
www.alentdesignsolutions.com
509.526.0682
----------------------------
next prev parent reply other threads:[~2004-08-24 22:37 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
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 [this message]
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=200408241544.59356.james@alentdesignsolutions.com \
--to=james@alentdesignsolutions.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.