From: Lennert Buytenhek <buytenh@wantstofly.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-arm dynamically linked binary problem
Date: Sat, 8 Jan 2005 15:01:51 +0100 [thread overview]
Message-ID: <20050108140151.GA25672@xi.wantstofly.org> (raw)
In-Reply-To: <200501051640.19489.paul@codesourcery.com>
On Wed, Jan 05, 2005 at 04:40:18PM +0000, Paul Brook wrote:
> I've just tired qemu CVS head, and that also works for me.
>
> However I'll I did need to rebuild from a clean source tree,
> ie "make clean && make" after changing things.
> There are obviously missing makefile dependencies somewhere.
I did that as well.
It seems that it doesn't matter which gcc version I use for compiling
the app. I can use gcc 3.4.2 compiled apps just fine, as long as I
use the glibc 2.1.3 dynamic linker. If I copy the glibc 2.3.2 ld.so
into my chroot (over the 2.1.3 one) things just go splat.
I'll play around with some other combinations as well.
--L
prev parent reply other threads:[~2005-01-08 14:20 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
2005-01-05 15:48 ` Lennert Buytenhek
2005-01-05 16:40 ` Paul Brook
2005-01-08 14:01 ` Lennert Buytenhek [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=20050108140151.GA25672@xi.wantstofly.org \
--to=buytenh@wantstofly.org \
--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).