From: "Wim Vanderbauwhede" <wim@motherearth.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Qemu-devel Digest, Vol 15, Issue 19 - WINE with QEMU on non-86x processor?
Date: Sat, 5 Jun 2004 20:56:43 -0000 [thread overview]
Message-ID: <twig.1086469003.86161@all2all.org> (raw)
In-Reply-To: <E1BWhiS-0006Mt-00@moses.all2all.org>
Hi Sander,
I have wine on qemu on an iBook rev 2.2. Basically, what you need is a number
of x86 RPMS (glibc and wine, but also som XFree stuff, binutils etc. I used
Red Hat 9, because unfortunately Mandrake doesn't work with qemu and Fedora
more or less breaks wine due to the execshield. Hence Red Hat 9.
I used rpm2cpio and cpio to "install" these RPM's in a folder and point qemu
to it.
I can give you more details (list of RPMS, cpio commands, qemu configuration)
after the weekend as my iBook is at work.
Cheers,
Wim
> Yes , I read it...............about 6 times over and over..........
> On non x86 CPUs, you need first to download at least an x86 glibc
> (`qemu-runtime-i386-XXX-.tar.gz' 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:
>
> x86 glibc? I have really no idea how to pull this off. Is somebody able to
> make a bit noob friendly manual of this? I'm not exactly a qeeky but not very
> stupid either but have no idea how to do this. I can't find a x86 glibc and
> have no idea what to do with it.
> I compiled QEMU and running windows 98 and that works. But I want to run WINE
> with QEMU in user mode since that gives more speed......
>
> Op zaterdag 5 juni 2004 20:50, schreef John R. Hogerhuis:
> > Don't know how PPC would be different, but you didn't say whether you
> > saw this...
> >
> > http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC31
> >
> > On Sat, 2004-06-05 at 05:55, Sander Nagtegaal wrote:
> > > Did anybody succeed in running WINE with QEMU on a PPC or other non 86x
> > > proccesor? I'd like to run QEMU in user mode and then start up WINE but
> > > so far I have no idea how to do it.......
> > > Any tips?
--
If it's pointless, what's the point?
If there is a point to it, what's the point?
(Tibor Fischer, "The Thought Gang")
next parent reply other threads:[~2004-06-05 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1BWhiS-0006Mt-00@moses.all2all.org>
2004-06-05 20:56 ` Wim Vanderbauwhede [this message]
[not found] ` <200406052312.04434.trunks-carracho@planet.nl>
2004-06-07 8:29 ` [Qemu-devel] Re: Qemu-devel Digest, Vol 15, Issue 19 - WINE with QEMU on non-86x processor? Wim Vanderbauwhede
[not found] ` <200406071153.13888.trunks-carracho@planet.nl>
2004-06-07 10:27 ` Wim Vanderbauwhede
[not found] ` <200406071535.27517.trunks-carracho@planet.nl>
2004-06-07 13:55 ` [Qemu-devel] Re: WINE with QEMU on PPC Wim Vanderbauwhede
2004-06-07 16:02 ` Sander Nagtegaal
2004-06-07 17:51 ` Mark Guertin
2004-06-07 20:07 ` Wim Vanderbauwhede
[not found] ` <200406072332.06794.trunks-carracho@planet.nl>
2004-06-07 21:36 ` Sander Nagtegaal
2004-06-07 22:10 ` Sander Nagtegaal
2004-06-08 7:12 ` Wim Vanderbauwhede
2004-06-08 8:54 ` Sander Nagtegaal
[not found] ` <1086685662.3281.4.camel@sicilia>
[not found] ` <200406081553.31093.trunks-carracho@planet.nl>
2004-06-08 14:10 ` [Qemu-devel] Re: WINE with QEMU on PPC: importance of gcc/glibc versions? Sander Nagtegaal
2004-06-09 7:57 ` Wim Vanderbauwhede
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=twig.1086469003.86161@all2all.org \
--to=wim@motherearth.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 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.