From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-ppc can't run static uClibc binaries.
Date: Sun, 28 Feb 2010 22:05:25 +0100 [thread overview]
Message-ID: <20100228210525.GU10291@volta.aurel32.net> (raw)
In-Reply-To: <20100216082145.GA23689@miranda.arrow>
On Tue, Feb 16, 2010 at 08:21:45AM +0000, Stuart Brady wrote:
> On Mon, Feb 15, 2010 at 12:19:24PM +0100, Alexander Graf wrote:
> > So what you really want is something like
> >
> > #ifdef CONFIG_LINUX_USER
> > /* exec return value is always 0 */
> > env->gpr[3] = 0;
> > #endif
> >
> > just after the #endif in your patch. If you had inlined your patch I could've commented it there.
>
> I've clearly misunderstood something, but isn't CONFIG_LINUX_USER always
> going to be defined when building linux-user/elfload.c, and doesn't
> CONFIG_BSD relate to the host that you're building for, not the target?
Yes, CONFIG_LINUX_USER will always be defined in linux-user/elfload.c,
while CONFIG_BSD_USER will always be defined in bsd-user/elfload.c. The
same way using CONFIG_BSD in linux-user/elfload.c doesn't make sense,
as this code will never been compiled.
> I can't remember whether Jocelyn was interested in running BSD binaries
> under Linux or under BSD. The former seems reasonable, although even if
> that did work for PPC at one point, I doubt that's still the case...
>
That's sound strange, if you do that I think you will need to use the
bsd-user code, not the linux-user code.
I have to say I don't really understand the reason why this BSD code is
there.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2010-02-28 21:05 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 11:20 [Qemu-devel] qemu-ppc can't run static uClibc binaries Rob Landley
2010-02-11 12:32 ` Alexander Graf
2010-02-14 8:36 ` Rob Landley
2010-02-14 14:41 ` Alexander Graf
2010-02-15 11:10 ` Rob Landley
2010-02-15 11:19 ` Alexander Graf
2010-02-15 12:58 ` Rob Landley
2010-02-15 13:01 ` Alexander Graf
2010-02-16 18:31 ` Rob Landley
2010-02-16 18:36 ` Alexander Graf
2010-02-16 19:14 ` Rob Landley
2010-02-15 13:08 ` [Qemu-devel] " Michael S. Tsirkin
2010-02-16 0:52 ` Rob Landley
2010-02-16 9:31 ` Alexander Graf
2010-02-16 18:14 ` Rob Landley
2010-02-17 9:24 ` Artyom Tarasenko
2010-02-17 15:45 ` Paolo Bonzini
2010-02-17 18:55 ` Rob Landley
2010-02-17 20:46 ` Blue Swirl
2010-02-18 11:38 ` Artyom Tarasenko
2010-02-18 13:17 ` Rob Landley
2010-02-18 14:10 ` Artyom Tarasenko
2010-02-18 13:05 ` Rob Landley
2010-02-18 11:21 ` Artyom Tarasenko
2010-02-18 13:14 ` Rob Landley
2010-02-18 14:19 ` Artyom Tarasenko
2010-02-20 17:17 ` [Qemu-devel] Fun with sparc (was Re: qemu-ppc can't run static uClibc binaries.) Rob Landley
2010-02-20 17:34 ` [Qemu-devel] " Blue Swirl
2010-02-20 18:38 ` Rob Landley
2010-02-20 21:59 ` Blue Swirl
2010-02-20 23:12 ` Rob Landley
2010-02-21 16:25 ` Commit 085219f79cad broke Sparc-32 back in 2.6.28 Rob Landley
2010-02-21 16:25 ` [Qemu-devel] " Rob Landley
2010-02-21 23:57 ` David Miller
2010-02-21 23:57 ` [Qemu-devel] " David Miller
2010-02-22 0:28 ` Bartlomiej Zolnierkiewicz
2010-02-22 0:28 ` [Qemu-devel] " Bartlomiej Zolnierkiewicz
2010-02-22 2:03 ` Rob Landley
2010-02-22 2:03 ` [Qemu-devel] " Rob Landley
2010-02-22 2:06 ` David Miller
2010-02-22 2:06 ` [Qemu-devel] " David Miller
2010-03-27 3:35 ` Rob Landley
2010-03-27 3:37 ` David Miller
2010-03-27 7:44 ` Rob Landley
2010-03-27 23:31 ` David Miller
2010-02-20 21:59 ` [Qemu-devel] Re: Fun with sparc (was Re: qemu-ppc can't run static uClibc binaries.) Artyom Tarasenko
2010-02-20 21:39 ` Artyom Tarasenko
2010-02-20 22:03 ` Blue Swirl
2010-02-17 16:36 ` [Qemu-devel] Re: qemu-ppc can't run static uClibc binaries Rob Landley
2010-02-16 8:21 ` [Qemu-devel] " Stuart Brady
2010-02-28 21:05 ` Aurelien Jarno [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=20100228210525.GU10291@volta.aurel32.net \
--to=aurelien@aurel32.net \
--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.