[Qemu-devel] Re: Qemu-devel Digest, Vol 15, Issue 19 - WINE with QEMU on non-86x processor?

[Wim Vanderbauwhede]

Seems like you've been moving fast in the meanwhile. Anyway, here's what
I did:
-get and compile qemu (was then qemu-0.5.3)
-get following RPMS:

ash-0.3.8-8.i386.rpm
bash-2.05b-20.i386.rpm
compat-libstdc++-7.3-2.96.118.i386.rpm
coreutils-4.5.3-19.i386.rpm
glib-1.2.10-10.i386.rpm
glibc-2.3.2-11.9.i386.rpm
gtk+-1.2.10-25.i386.rpm
libgcc-3.2.2-5.i386.rpm
libjpeg-6b-26.i386.rpm
libstdc++-3.2.2-5.i386.rpm
libtermcap-2.0.8-35.i386.rpm
libungif-4.1.0-15.i386.rpm
XFree86-4.3.0-2.i386.rpm
XFree86-libs-4.3.0-2.90.55.i386.rpm
zlib-1.1.4-8.i386.rpm

wine-20040309-1rh9winehq.i386.rpm (or more recent)

-Put them in the target platform directory (mine is /home/ARCHS/rh_x86)
-Install the rpm's using rpm2cpio and cpio: 
e.g. 
$ rpm2cpio ash-0.3.8-8.i386.rpm | cpio -idv

-I assume you know how to set up wine (I mean adapting the
~/.wine/config file). My qemu-wine home directory is usr/share/wine-c in
the target platform directory. If you like I can mail my .wine/config
file.

-To actually run Windows applications under wine under qemu, I use these
commands (it's clumsy, I know. If you configure your system to call qemu
automatically for x86 binaries, it would be a lot cleaner. I just put
the commands in a small shell script): 

$ declare -x WINEDLLPATH="/home/ARCHS/rh_x86/usr/lib/wine"
$ declare -x
LD_LIBRARY_PATH="/home/ARCHS/rh_x86/usr/lib:/home/ARCHS/rh_x86/usr/X11R6/lib"
$ qemu-i386 -L /home/ARCHS/rh_x86 /home/ARCHS/rh_x86/usr/bin/wineserver
$ qemu-i386 -L /home/ARCHS/rh_x86
/home/ARCHS/rh_x86/usr/bin/wine-pthread
/home/ARCHS/rh_x86/usr/share/wine-c/windows/notepad.exe

-To conclude, I must say it didn't work very well for me, but that was
mostly due to wine, not to qemu. The problem is that most installers
fail under wine. But I guess if you have Windows, install stuff there
and then copy to wine, that should work well.

HTH,

Wim


On Sat, 2004-06-05 at 22:12, Sander Nagtegaal wrote:
> Thanks. Hope to hear from you how you did it soon. I really haven't been able 
> to find good information.
> I'm using Yellowdog Linux 3.0.1 now ( red hat based )
> 
> Op zaterdag 5 juni 2004 22:56, schreef u:
> > 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?
> 
>