Thanks for your reply. At 2018-10-30 16:33:15, "Peter Maydell" <peter.mayd...@linaro.org> wrote: >On 30 October 2018 at 02:16, wj193102 <wj193...@163.com> wrote: >> Hi, everyone. >> When I have installed the QEMU3.0.0 in the Linux on non X86 CPUS, I want >> to use user space emulator to run Wine. I can get the source code for Wine >> and the RPM file for Wine from the WineHQ web page. >> I used to compile Wine in the X86-based Linux system and used it to run most >> Win32 programs. Now I want to use it on the non X86 CPUS by QEMU. But I >> can't get the function to install and use the Wine. Please give me some >> advice >> or some functions to finish it. Thanks a lot. > >I'm afraid you will need to provide more detail for us to >help here. What exactly are you doing? Which commands are you >running? What is the exact error message or failure you see?
I have installed the Wine in Linux(fedora) on the X86 CPUs from the source code. Can I copy the related file of Wine from the Linux on X86 CPUs to the Linux on the non X86 CPUS for running the command "wine" or "winecfg". >> Meanwhile, I use the command "qemu-i386/qemu-x86_64 *.sh" to >> run the application from the X86 CPUS on non X86 CPUS, I get the >> error information:"Invalid ELF image for this architecture". Why >> the error is comming? What can I do to resolve this problem? > >This is probably because you are trying to run a shell script. >(I'm guessing this from the '.sh' extension). This won't work. >QEMU only runs actual executables (ELF files). That is my fault. I don't run the *.sh file. I copy the file "/bin/ls" from the Linux on x86 CPUs to the Linux on non X86 CPUs. I put the file in the new created directory, such as "/home/admin/user/test/". Then I run the executable file,using "qemu-i386 ./ls", I get the following error: "./ls: error while loading shared libraries: libselinux.so.1: cannot open shared object file: No such file or directory." How can I resolve this problem? >Usually the setup is that the host Linux system is set up >with binfmt-misc, so that if it encounters a guest-architecture >binary it will automatically run it under QEMU. Usually >this is done to allow running guest binaries inside a chroot. > >thanks >-- PMM Thanks a lot. --WangJi
