Re: [Qemu-devel] WINE with QEMU on non-86x processor?

[Sander Nagtegaal]

No........I did nothing special.......the unset thing I didn't do.......
I just moved the stuff to the standard directory it should be.
The documentation is not really incomplete but just a bit to vague for a 
stupid noob like me.......
I didn't put the files from the /usr directory that you get when you unpack 
the files in the normal /usr directory. It unpacked a /usr in my home 
directory but didn't think about the fact that I should move it to my normal 
/usr directory. The manual didn't say it and since I'm still learning about 
Linux that didn't cross my mind. After I moved the "local" dir files to my 
normal "local" dir and the "usr" dir files to my normal "usr" dir it worked.
So it's just because I'm too nooby that it didn't work. However it would be 
nice to say in the docu that people should move the unpacked files to their 
normal system locations. That might help alot of "noobs" like me.
Now only I need to figure out how to configure WINE.
Any help what to with the script or what else to do with it?
The script contents are..............

# wine config for qemu
WINE_PATH=/usr/local/wine-i386

export PATH=$PATH:$WINE_PATH/bin

# only create new config if none is present
if [ '!' -d $HOME/.wine ] ; then
    mkdir $HOME/.wine
    cp $WINE_PATH/etc/* $HOME/.wine
fi

# only create wine c: drive if none exists
if [ '!' -d $HOME/wine ] ; then
    cp -r $WINE_PATH/wine $HOME
fi

if [ '!' -d "$HOME/wine/Program Files/qemu" ] ; then
    cp -r "$WINE_PATH/wine/Program Files/qemu" "$HOME/wine/Program Files"
fi


Thnx!

Op zondag 6 juni 2004 19:28, schreef u:
> Hi Sander,
>
> While it is still fresh in your mind, please post to the list what gaps
> you had to fill in the documentation so that it can be fixed. I suppose
> you had to do the unset. What was the command line you finally used? Did
> you need to put the -L option with a path?
>
> Thanks
>
> -- John.
>
> On Sun, 2004-06-06 at 10:10, Sander Nagtegaal wrote:
> > THNX MAN! I did it..........(well with a bit of help ;-))
> > My ls x86 file now works. Gonna try WINE..........i'll keep you informed.
> > They should really write a new manual................
> >
> > Op zondag 6 juni 2004 18:57, schreef u:
> > > 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.