qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] Arm arch5 support
Date: Mon, 2 Aug 2004 00:03:03 +0100	[thread overview]
Message-ID: <200408020003.03091.paul@codesourcery.com> (raw)
In-Reply-To: <20040801221610.GA5597@xi.wantstofly.org>

On Sunday 01 August 2004 23:16, Lennert Buytenhek wrote:
> On Sun, Aug 01, 2004 at 11:38:44PM +0200, Lennert Buytenhek wrote:
> > Your armv4 binaries do work, so do you maybe have any suggestions
> > for a target triple I should use?
>
> I didn't mean to sound as if I don't believe you.. in fact, I
> vaguely remember having succeeded in running ARM binaries in
> the past, but can't remember how and when.  I'm just wondering
> what you're doing differently that causes it to work for you,
> and not for me and some other people on this list who've tried
> in the past.

arm-linux, armv4-linux adn armv5te-redhat-linux-gnu toolchains all work.
I've run the gcc testsuite on the arm-linux, and am only getting a handful of 
unexpected failures. The other two I've only verified that "Hello World" 
works.

The toolchains I've built are all configured for static libraries only.
I have run dynamically linked programs from a debian-arm chroot.

FWIW I'm using CVS HEAD binutils and glibc, and a very slightly modified 
csl-arm (CodeSourcery) gcc.

qemu from cvs head as of yesterday

Paul

  reply	other threads:[~2004-08-01 23:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-01 17:08 [Qemu-devel] [patch] Arm arch5 support Paul Brook
2004-08-01 17:41 ` Lennert Buytenhek
2004-08-01 18:32   ` Paul Brook
2004-08-01 21:38     ` Lennert Buytenhek
2004-08-01 22:16       ` Lennert Buytenhek
2004-08-01 23:03         ` Paul Brook [this message]
2004-08-01 23:14         ` 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=200408020003.03091.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).