qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "John R. Hogerhuis" <jhoger@speakeasy.net>
To: Sander Nagtegaal <trunks-carracho@planet.nl>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] WINE with QEMU on non-86x processor?
Date: Sun, 06 Jun 2004 09:57:25 -0700	[thread overview]
Message-ID: <1086541045.14163.217.camel@aragorn> (raw)
In-Reply-To: <200406061434.46109.trunks-carracho@planet.nl>

The first thing you need to accomplish is get x86  ls to work. WINE is
really complex, so at best it should be the second thing you run.

QEMU doesn't require much in the way of installation. I'd guess it is
more likely that your x86 libraries are not being found.

Did you try these instructions from the web page?


        On non x86 CPUs, you need first to download at least an x86
        glibc (`qemu-runtime-i386-XXX-.tar.gz' [FILENAME IS DIFFERENT]
        on the QEMU web page). Ensure that LD_LIBRARY_PATH is not set: 
        unset LD_LIBRARY_PATH 
        
         Then you can launch the precompiled `ls' x86 executable: 
        qemu-i386 tests/i386/ls

Now the previous command shows a -L /   option for X86 which is how you
tell QEMU where to look for libraries. You probably should unset the
library path as above, and when you invoke QEMU give an -L command but
with the path to your x86 libraries. I'm not sure why this is not shown
in the documentation, I could be wrong or it could be an oversight.

Someone experienced with qemu AND has a PPC (or actually any non x86
arch), please help Sander out by trying this... and then post to the
list exactly what you did so that the doco can be updated.

-- John.

  reply	other threads:[~2004-06-06 16:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-05 10:41 [Qemu-devel] Cirrus VGA Fabrice Bellard
2004-06-05 12:50 ` Karel Gardas
2004-06-05 12:55   ` [Qemu-devel] WINE with QEMU on non-86x processor? Sander Nagtegaal
2004-06-05 18:50     ` John R. Hogerhuis
2004-06-05 19:09       ` Sander Nagtegaal
2004-06-05 20:32         ` John R. Hogerhuis
     [not found]   ` <1086483144.29235.173.camel@aragorn>
     [not found]     ` <200406061358.35817.trunks-carracho@planet.nl>
2004-06-06 12:34       ` Sander Nagtegaal
2004-06-06 16:57         ` John R. Hogerhuis [this message]
2004-06-06 17:14           ` Sander Nagtegaal
     [not found]   ` <200406061910.03637.trunks-carracho@planet.nl>
     [not found]     ` <1086542927.14163.228.camel@aragorn>
2004-06-06 17:37       ` Sander Nagtegaal
2004-06-06 17:43         ` Sander Nagtegaal
2004-06-05 12:55 ` [Qemu-devel] Cirrus VGA Antony T Curtis
2004-06-05 14:16   ` Juergen Lock
     [not found]     ` <1086448947.6650.358.camel@pcgem.rdg.cyberkinetica.com>
2004-06-05 20:46       ` Juergen Lock

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=1086541045.14163.217.camel@aragorn \
    --to=jhoger@speakeasy.net \
    --cc=jhoger@pobox.com \
    --cc=qemu-devel@nongnu.org \
    --cc=trunks-carracho@planet.nl \
    /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).