[Qemu-devel] Re: WINE with QEMU on PPC: importance of gcc/glibc versions?

[Sander Nagtegaal]

> I tried it with the redhat RPMS........same problem......only ash.static
> works.......
> By the way......how can I safely update my glibc?
>
> So new summary:
> > -Red Hat 9 on qemu 0.5.5 compiled with gcc 3.3.2 and glibc-2.3.3 works
> > -Red Hat 9 on qemu 0.5.5 compiled with gcc 3.2.2 and glibc-2.3.1 does
> > not work (segfaults)
> > -Red Hat 7.3 on qemu 0.5.5. compiled with gcc 3.2.2 and glibc-2.3.1 does
> > not
>
> work ( segfaults )
>
> > And indeed, the static binaries do work.
>
> Op dinsdag 8 juni 2004 11:07, schreef u:
> > I notice that I have gcc 3.3.2 and glibc-2.3.3
> > I know it's hard to upgrade glibc (it's almost a surefire way to break
> > your system), but you might try to upgrade your gcc first.
> > Or, indeed, you might try Red Hat 7.3, as these binaries have been
> > compiled with an older gcc.
> >
> > qemu-gurus, does this make sense to any of you? In summary:
> > -Red Hat 9 on qemu 0.5.5 compiled with gcc 3.3.2 and glibc-2.3.3 works
> > -Red Hat 9 on qemu 0.5.5 compiled with gcc 3.2.2 and glibc-2.3.1 does
> > not work (segfaults)
> > And indeed, the static binaries do work.
> >
> > On Tue, 2004-06-08 at 09:54, Sander Nagtegaal wrote:
> > > address@hidden azrael]$ rpm -q gcc
> > > gcc-3.2.2-2a
> > > address@hidden azrael]$ rpm -q glibc
> > > glibc-2.3.1-51a
> > >
> > > address@hidden azrael]$ qemu-i386 -L /home/azrael/Emulation/
> > > /home/azrael/Emulation/bin/ash.static -c pwd
> > > /home/azrael
> > >
> > > The ash.static works.......
> > >
> > > address@hidden azrael]$ qemu-i386 -L /home/azrael/Emulation/
> > > /home/azrael/Emulation/bin/sh -c pwd
> > > qemu: uncaught target signal 11 (Segmentation fault) - exiting
> > >
> > > The sh does not........
> > >
> > > address@hidden azrael]$ qemu-i386 -L /home/azrael/Emulation/
> > > /home/azrael/Emulation/bin/pwd
> > > qemu: uncaught target signal 11 (Segmentation fault) - exiting
> > >
> > > And neither does pwd.............
> > > So I should try and download the redhat 7.3 RPMS x86 and try them out?
> > >
> > > Op dinsdag 8 juni 2004 09:12, schreef u:
> > > > > Just tested something..........it gives the same error with
> > > > > non-existed directories.
> > > >
> > > > That must be the root of the problem then.
> > > > Did you set the LD_LIBRAY_PATH correctly?
> > > >
> > > > What version of glibc and gcc do you have?
> > > > $ rpm -q gcc
> > > > $ rpm -q glibc
> > > >
> > > > Could you test this:
> > > > $ qemu-i386 -L /yourpath /yourpath/bin/ash.static -c pwd
> > > > $ qemu-i386 -L /yourpath /yourpath/bin/sh -c pwd
> > > > $ qemu-i386 -L /yourpath /yourpath/bin/pwd
> > > >
> > > > Now, I had this problem with Mandrake 10 x86, and none of the gurus
> > > > could explain it. That's why I switched to Red Hat 9. It that fails
> > > > for you, you could maybe try Red Hat 7.3.
> > > >
> > > > Sander Nagtegaal <address@hidden> said:
> > > > > Just tested something..........it gives the same error with
> > > > > non-existed directories. It does not give the error when not using
> > > > > the -L option but then it can't find some libraries.........
> > > > >
> > > > > Hope you know what to do........
> > > > >
> > > > > Thanks , Sander
> > > > >
> > > > > Op maandag 7 juni 2004 23:32, schreef u:
> > > > > > With the -L option error returns.
> > > > > >
> > > > > > address@hidden ****]$ qemu-i386 -L /home/*****/Emulation
> > > > > > /home/******/Emulation/usr/bin/wineserver
> > > > > > qemu: uncaught target signal 11 (Segmentation fault) - exiting
> > > > > >
> > > > > > So it still doesn't work sadly...........I think I'm very close.
> > > > > > Would a CVS qemu help maybe?
> > > > > >
> > > > > > Op maandag 7 juni 2004 22:07, schreef u:
> > > > > > > It looks like you forgot the -L option.
> > > > > > >
> > > > > > > Sander Nagtegaal <address@hidden> said:
> > > > > > > > address@hidden Emulation]$ qemu-i386
> > > > > > > > /home/azrael/Emulation/usr/bin/wineserver
> > > > > > > > /home/azrael/Emulation/usr/bin/wineserver: /lib/libc.so.6:
> > > > > > > > version `GLIBC_2.2' not found (required by
> > > > > > > > /home/azrael/Emulation/usr/bin/wineserver)
> > > > > > > > /home/azrael/Emulation/usr/bin/wineserver: /lib/libc.so.6:
> > > > > > > > version `GLIBC_2.3' not found (required by
> > > > > > > > /home/azrael/Emulation/usr/bin/wineserver)
> > > > > > > > /home/azrael/Emulation/usr/bin/wineserver: /lib/libc.so.6:
> > > > > > > > version `GLIBC_2.2' not found (required by
> > > > > > > > /home/azrael/Emulation/usr/lib/libwine.so.1)
> > > > > > > > /home/azrael/Emulation/usr/bin/wineserver: /lib/libc.so.6:
> > > > > > > > version `GLIBC_2.3' not found (required by
> > > > > > > > /home/azrael/Emulation/usr/lib/libwine_unicode.so.1)
> > > > > > > >
> > > > > > > > I'm a step further. The 11 error was just that I didn't
> > > > > > > > correctly put the LD path with declare -x
> > > > > > > > Doing that solved my problem.
> > > > > > > > But now wineserver only can't find 4 pieces. Where to get
> > > > > > > > them? I installed every rpm you said and everything is found
> > > > > > > > except for those 4.........
> > > > > > > >
> > > > > > > > Op maandag 7 juni 2004 15:55, schreef u:
> > > > > > > > > On Mon, 2004-06-07 at 13:36, Sander Nagtegaal wrote:
> > > > > > > > > > -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
> > > > > > > > > >
> > > > > > > > > > Just a small question. Can I give the target platform
> > > > > > > > > > directory any name I want? And then just change the dir?
> > > > > > > > > > Or does it have to be a /ARCHS/rh_x86 type of directory?
> > > > > > > > >
> > > > > > > > > It can be any name you like. I just mentioned the name I
> > > > > > > > > gave because it also occurs in the config file.
> > > > > > > > >
> > > > > > > > > On Mon, 2004-06-07 at 14:35, Sander Nagtegaal wrote:
> > > > > > > > > > groff: error while loading shared libraries:
> > > > > > > > > > /home/azrael/Emulation/usr/lib/libstdc++.so.5: ELF file
> > > > > > > > > > data encoding not big-endian
> > > > > > > > > >
> > > > > > > > > > Another thing is that when I now run a "man **** "
> > > > > > > > > > command it gives errors. All my man pages are not working
> > > > > > > > > > anymore.........maybe some declare path is wrong?
> > > > > > > > >
> > > > > > > > > I'm afraid that's normal: your LD_LIBRARY_PATH now points
> > > > > > > > > to the x86 libraries. If you just open a new terminal
> > > > > > > > > window, and run "man" there, that should be OK.
> > > > > > > > > To avoid this kind of problem, I put my qemu-specific
> > > > > > > > > commands in shell scripts. The "declare" statements are
> > > > > > > > > only valid within the enviroment of the script, not outside
> > > > > > > > > it.
> > > > > > > > >
> > > > > > > > > On Mon, 2004-06-07 at 14:26, Sander Nagtegaal wrote:
> > > > > > > > > > address@hidden Emulation]$ qemu-i386 -L
> > > > > > > > > > /home/azrael/Emulation
> > > > > > > > > > /home/azrael/Emulation/usr/bin/wineserver
> > > > > > > > > > qemu: uncaught target signal 11 (Segmentation fault) -
> > > > > > > > > > exiting
> > > > > > > > > >
> > > > > > > > > > That's what I got trying to run winserver. What could be
> > > > > > > > > > the problem?
> > > > > > > > >
> > > > > > > > > The wineserver error is a different issue. What qemu are
> > > > > > > > > you using? I am now using qemu-0.5.5, and wine-20040505;
> > > > > > > > > before, I used qemu-0.5.3 and wine-20040309.
> > > > > > > > > I have glibc-2.3.3 and I use gcc-3.3.2 for building.
> > > > > > > > > But I'm just a user, segfaults in qemu is something for the
> > > > > > > > > real qemu-guru's.
> > > > > > > > >
> > > > > > > > > Cheers,
> > > > > > > > >
> > > > > > > > > Wim
> > > > > > > > >
> > > > > > > > > > Op maandag 7 juni 2004 12:27, schreef u:
> > > > > > > > > > > In attachment my wine config file. Save it as
> > > > > > > > > > > ~/.wine/config and edit the "Path" entries under the
> > > > > > > > > > > [Drive ...] entries a bit so that all paths point to
> > > > > > > > > > > meaningful directories:
> > > > > > > > > > >
> > > > > > > > > > > [Drive C]
> > > > > > > > > > > "Path"="/home/ARCHS/rh_x86/usr/share/wine-c"
> > > > > > > > > > > "Type" = "hd"
> > > > > > > > > > > "Label" = "MS-DOS"
> > > > > > > > > > > "Filesystem" = "win95"
> > > > > > > > > > >
> > > > > > > > > > >   [Drive D] "Path" = "/mnt/cdrom"
> > > > > > > > > > > "Type" = "cdrom"
> > > > > > > > > > > "Label" = "CD-Rom"
> > > > > > > > > > > "Filesystem" = "win95"
> > > > > > > > > > > ; make sure that device is correct and has proper
> > > > > > > > > > > permissions ! "Device" = "/dev/cdrom"
> > > > > > > > > > >
> > > > > > > > > > >     [Drive E] "Path" = "/tmp"
> > > > > > > > > > > "Type" = "hd"
> > > > > > > > > > > "Label" = "Tmp Drive"
> > > > > > > > > > > "Filesystem" = "win95"
> > > > > > > > > > >
> > > > > > > > > > >     [Drive F] "Path" = "/home/wim"
> > > > > > > > > > > "Type" = "network"
> > > > > > > > > > > "Label" = "Home"
> > > > > > > > > > > "Filesystem" = "win95"
> > > > > > > > > > >
> > > > > > > > > > >     [Drive G] "Path" = "/home/ARCHS/rh_x86"
> > > > > > > > > > > "Type" = "hd"
> > > > > > > > > > > "Label" = "MS-DOS"
> > > > > > > > > > > "Filesystem" = "win95"
> > > > > > > > > > >
> > > > > > > > > > > On Mon, 2004-06-07 at 10:53, Sander Nagtegaal wrote:
> > > > > > > > > > > > Op maandag 7 juni 2004 10:29, schreef u:
> > > > > > > > > > > > > -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.
> > > > > > > > > > > >
> > > > > > > > > > > > No......I do not know how to set up wine..That was my
> > > > > > > > > > > > next problem after I managed to let qemu run the "ls"
> > > > > > > > > > > > file. Could you mail the config or email me how to
> > > > > > > > > > > > set it up? Thanks alot! You're a great help. I'm
> > > > > > > > > > > > going to try it!