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 23:44:59 +0100 [thread overview]
Message-ID: <200408242344.59718.paul@codesourcery.com> (raw)
In-Reply-To: <200408241544.59356.james@alentdesignsolutions.com>
On Tuesday 24 August 2004 23:44, James Pellow wrote:
> 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.
No idea, sorry.
Paul
prev parent reply other threads:[~2004-08-24 22:49 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
2004-08-24 22:44 ` Paul Brook [this message]
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=200408242344.59718.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).