From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-arm dynamically linked binary problem
Date: Wed, 5 Jan 2005 15:20:35 +0000 [thread overview]
Message-ID: <200501051520.35978.paul@codesourcery.com> (raw)
In-Reply-To: <20050105134908.GE20925@xi.wantstofly.org>
On Wednesday 05 January 2005 13:49, Lennert Buytenhek wrote:
> On Wed, Jan 05, 2005 at 02:35:09PM +0100, Magnus Damm wrote:
> > Hello,
>
> Hello,
>
> > > I have three sets of {ld-linux,libc} for little-endian ARM: one from
> > > qemu-gnemul-0.5.1.tar.gz from the qemu site, one hand-built with gcc
> > > 3.3.4 and glibc 2.3.3, and one hand-built with gcc 3.4.2 and glibc
> > > 2.3.3. Yours works and mine don't.
> > >
> > > Is there anything special about your libraries? Which versions of
> > > gcc/glibc did you use to build them?
> >
> > I have not much experience with ARM, but have you tried to use a
> > toolchain built with crosstool? Maybe there are some patches there?
>
> Yes, I did build these with crosstool. I do have quite some experience
> with ARM platforms, and the binaries that all these toolchains generate
> do run just fine on 'real' ARM hardware.
>
> I just think there's something in qemu's ELF setup that the glibc 2.3
> dynamic linker doesn't like.
It working with a gcc3.4-csl/glibc2.3.3 soft-float armv4 toolchain.
> Inconsistency detected by ld.so: dymanic-link.h: 150: elf_get_dynamic_info:
> Assertion `info[20]->d_un.d_val == 17 || info[20]->d_un.d_val == 7' failed!
I remember seeing something like this. IIRC It was caused by the (recently
fixed) rrx bug.
Paul
next prev parent reply other threads:[~2005-01-05 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-31 18:21 [Qemu-devel] qemu-arm dynamically linked binary problem Lennert Buytenhek
2005-01-05 12:03 ` [Qemu-devel] " Lennert Buytenhek
2005-01-05 13:35 ` [Qemu-devel] " Magnus Damm
2005-01-05 13:49 ` Lennert Buytenhek
2005-01-05 15:20 ` Paul Brook [this message]
2005-01-05 15:48 ` Lennert Buytenhek
2005-01-05 16:40 ` Paul Brook
2005-01-08 14:01 ` Lennert Buytenhek
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=200501051520.35978.paul@codesourcery.com \
--to=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).