<span>On 8/8/07, Bryan DeGrendel <<a href="mailto:sirnuke@gmail.com">sirnuke@gmail.com</a>> wrote:<br>> On 8/8/07, Walter Graf <<a href="mailto:grafw@umich.edu">grafw@umich.edu</a>> wrote:<br>> > On 8/8/07, Bryan DeGrendel <
<a href="mailto:sirnuke@gmail.com">sirnuke@gmail.com</a>> wrote:<br>> > > On 8/7/07, Walter Graf <<a href="mailto:grafw@umich.edu">grafw@umich.edu</a>> wrote:<br>> > > > Hello, all,<br>> > > > I'm trying to get Wine running on some Red Hat boxes at my University
<br>> > (don't<br>> > > > worry, I have permission!) ... But, I don't have any root access to the<br>> > > > boxes, and I'm limited to installing on my shared (AFS) space. In any<br>
> > case,<br>> > > > I'd probably want it to run from my user space anyways, so that its<br>> > > > accessible from all boxes on the network.<br>> > > > Some required information, probably:
<br>> > > ><br>> > > > dc3nep68% cat /proc/version<br>> > > > Linux version 2.6.9-42.0.10.ELsmp<br>> > > > (<a href="mailto:brewbuilder@ls20-bc1-14.build.redhat.com">brewbuilder@ls20-bc1-14.build.redhat.com
</a>) (gcc version<br>> > > > 3.4.6 20060404 (Red Hat 3.4.6-3 )) #1 SMP Fri Feb 16 17:13:42 EST 2007<br>> > > ><br>> > > > When I log in, it greets me with:<br>> > > > CAEN Red Hat Enterprise Linux WS release 4 (Nahant Update 4)
<br>> > > ><br>> > > > I know, these boxes are pretty old. There's not much I can do about<br>> > that.<br>> > > > I tried to do an RPM install using --prefix=[somewhere in my AFS user
<br>> > > > space], but it tells me "wine is not relocatable." (I very well may have<br>> > > > done something wrong, as I'm not a RH guy. If anyone has suggestions on<br>> > this
<br>> > > > front, I'd gladly accept them, too!) So, I figured I'd have a go at<br>> > > > compiling. So,<br>> > > ><br>> > > > ./configure --prefix=[a folder in my AFS space] --without-opengl
<br>> > > > goes fine<br>> > > ><br>> > > > make depend<br>> > > > no problems<br>> > > ><br>> > > > make<br>> > > > goes ok for a bit, then (starting form the topmost error I can find):
<br>> > > ><br>> > > > gcc -m32 -c -I. -I. -I../../include -I../../include<br>> > > ><br>> > -DINCLUDEDIR="\"/afs/engin.umich.edu/u/g/r/grafw/Private/wine/include/wine\""
<br>> > > ><br>> > -DDLLDIR="\"/afs/engin.umich.edu/u/g/r/grafw/Private/wine/lib/wine\""<br>> > > ><br>> > -DLIBDIR="\"/afs/engin.umich.edu/u/g/r/grafw/Private/wine/lib\""
<br>> > > > -DDLLFLAGS="\"-D_REENTRANT -fPIC\"" -DLDDLLFLAGS="\"-shared<br>> > > ><br>> > -Wl,-Bsymbolic,-z,defs,-init,__wine_spec_init,-fini,__wine_spec_fini\""
<br>> > > > -DAS="\"as --32\"" -DCC="\"gcc -m32\"" -DCPP="\"cpp\"" -DCXX="\"g++\""<br>> > > > -DLD="\"ld -m elf_i386\""
<br>> > -DPRELINK="\"/usr/sbin/prelink\""<br>> > > > -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement<br>> > > > -Wwrite-strings -Wpointer-arith -g -O2 -o
winegcc.o winegcc.c<br>> > > > cc1: error: invalid option `32"'<br>> > > > cc1: error: missing argument to "-m"<br>> > > > cc1: error: unrecognized command line option "-f32""
<br>> > > > make[2]: *** [ winegcc.o] Error 1<br>> > > > make[2]: Leaving directory<br>> > > ><br>> > `/afs/engin.umich.edu/u/g/r/grafw/Private/wine-0.9.42/tools/winegcc'<br>> > > > make[1]: *** [winegcc] Error 2
<br>> > > > make[1]: Leaving directory<br>> > > > `/afs/engin.umich.edu/u/g/r/grafw/Private/wine-0.9.42<br>> > > > /tools'<br>> > > > make: *** [tools] Error 2<br>> > > >
<br>> > > > I've tried compiling with several versions of Wine (the exact error<br>> > above is<br>> > > > from 0.9.42, but I also got the same thing with 0.9.41 an 0.9.12)...<br>> > > > That's about it. Does anybody know what's going on here? Do I need to
<br>> > give<br>> > > > any other information?<br>> > > ><br>> > > > Thanks :D<br>> > > ><br>> > > > Walter<br>> > > ><br>> > > > _______________________________________________
<br>> > > > wine-users mailing list<br>> > > > <a href="mailto:wine-users@winehq.org">wine-users@winehq.org</a><br>> > > > <a href="http://www.winehq.org/mailman/listinfo/wine-users">http://www.winehq.org/mailman/listinfo/wine-users
</a><br>> > > ><br>> > ><br>> > > Hello. I spend some time get a half-decent music player to compile on<br>> > > my AFS space a few months ago. A few notes:<br>> > ><br>> > > 1. I believe all CAEN computers are 64-bit. -m32 flag means compile a
<br>> > > 32-bit program for a 64-bit OS, if I understand correctly. It looks<br>> > > like you need the glibc-devel 32-bit package for that to work [1].<br>> > > 2. There weren't many dev libraries installed on the box I was on. I
<br>> > > guess if ./configure ran okay there aren't any show stopping problems,<br>> > > but you might want to try the --verbose flag to see what you are<br>> > > missing.<br>> > >
<br>> > > I don't have any experience with WINE on 64-bit but you might want to<br>> > > read this [2] page.<br>> > ><br>> > > Good luck,<br>> > > Bryan DeGrendel<br>> > >
<br>> > > [1]<br>> > <a href="http://www.redhat.com/archives/fedora-devel-list/2005-January/msg00831.html">http://www.redhat.com/archives/fedora-devel-list/2005-January/msg00831.html</a><br>> > > [2]
<a href="http://wiki.winehq.org/WineOn64bit">http://wiki.winehq.org/WineOn64bit</a><br>> ><br>> ><br>> > Thanks for the reply..!<br>> > I certainly hadn't considered that these machines were 64 bit.. When
<br>> > compiling your music player, did you also end up using glibc-devel? How did<br>> > you get this working (that is, without root access)? I haven't had any luck<br>> > so far.<br>> <br>> My music player didn't require to be compiled under 32-bit. I did
<br>> have to install a few libraries to my own home directory to get it to<br>> work (the program's configure script allowed me to set the location<br>> for each individual library and headers). It was quite a bit of work,
<br>> and I only managed to get the ncurses UI to work. The music player<br>> (Zinf, for the record) is a very simple piece of software.<br>> <br>> ./configure --help give this:<br>> --enable-win64 build a Win64 emulator on AMD64 (won't run
<br>> Win32 binaries)<br>> <br>> Which should hopefully get around the lack of 32-bit libraries, at the<br>> price only being able to run 64-bit windows software.<br>> <br>> You could potentially install the glibc-devel-i386 package to your
<br>> home directory. However, this probably isn't a fairly simple case of<br>> setting the include path.<br>> <br>> Another option is to manually extract the RPM [3].<br>> <br>> > And, good call on the ./compile --verbose ... it looks like I'll be missing
<br>> > quite a few things, but nothing that I really need, I think. I'm currently<br>> > only planning on using one program through Wine.<br>> ><br>> > Thanks again,<br>> ><br>> > Walter
<br>> ><br>> <br>> Sincerely,<br>> Bryan DeGrendel<br>> <br>> [3] <a href="http://www.ideaspace.net/users/wkearney/archives/entries/000568.html">http://www.ideaspace.net/users/wkearney/archives/entries/000568.html
</a><br>> <br><br>Again, thanks for the reply..!<br><br>Manually extracting the RPM sounded like the best idea to me. The extracting part went without problem, however, when I try to run wine, it shouts:<br><br>usr/bin/wine: error while loading shared libraries:
libwine.so.1: cannot open shared object file: No such file or directory<br><br>Fine, I think. I've got this file in ~/Private/wine/usr/lib/ .. so I'll run<br></span>strace -o ~/error.log usr/bin/wine <br>to see where its trying to pull this file, and symlink it..!. Almost needless to say, it tries a bunch of different places, mostly around /usr/lib/ .. but they're all places where I'd need root access to stick a symlink. I've hit a wall on this front.
<br><br><br>So, lets try compiling. Installing <span>glibc-devel-i386 to my home doesn't sound like something I can really accomplish, so, l</span>ike you suggested, this time I ran ./configure --enable-win64 .. and this went fine. Again, make depend also went fine. But, make gave me the following (different) error which I've not been able to trace down.
<br><br><span>gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -DWINE_UNICODE_API="" -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -D__x86_64__ -o
casemap.o casemap.c<br>In file included from ../../include/windef.h:234,<br> from ../../include/wine/unicode.h:26,<br> from casemap.c:4:<br>../../include/winnt.h:619: error: width of `NextEntry' exceeds its type
<br>../../include/winnt.h:622: error: width of `Reserved' exceeds its type<br>../../include/winnt.h:627: error: width of `Sequence' exceeds its type<br>../../include/winnt.h:631: error: width of `NextEntry' exceeds its type
<br>In file included from ../../include/windef.h:234,<br> from ../../include/wine/unicode.h:26,<br> from casemap.c:4:<br>../../include/winnt.h:831:1: warning: "CONTEXT_CONTROL" redefined
<br>../../include/winnt.h:786:1: warning: this is the location of the previous definition<br>../../include/winnt.h:832:1: warning: "CONTEXT_INTEGER" redefined<br>../../include/winnt.h:787:1: warning: this is the location of the previous definition
<br>../../include/winnt.h:833:1: warning: "CONTEXT_SEGMENTS" redefined<br>../../include/winnt.h:788:1: warning: this is the location of the previous definition<br>../../include/winnt.h:834:1: warning: "CONTEXT_FLOATING_POINT" redefined
<br>../../include/winnt.h:789:1: warning: this is the location of the previous definition<br>../../include/winnt.h:835:1: warning: "CONTEXT_DEBUG_REGISTERS" redefined<br>../../include/winnt.h:790:1: warning: this is the location of the previous definition
<br>../../include/winnt.h:836:1: warning: "CONTEXT_FULL" redefined<br>../../include/winnt.h:791:1: warning: this is the location of the previous definition<br>../../include/winnt.h:952: error: conflicting types for 'CONTEXT'
<br>../../include/winnt.h:793: error: previous declaration of 'CONTEXT' was here<br>make[2]: *** [casemap.o] Error 1<br>make[2]: Leaving directory `/afs/engin.umich.edu/u/g/r/grafw/Private/wine-0.9.42/libs/wine'
<br>make[1]: *** [wine] Error 2<br>make[1]: Leaving directory `/afs/engin.umich.edu/u/g/r/grafw/Private/wine-0.9.42/libs'<br>make: *** [libs] Error 2<br><br><br>Looks kindof creepy to me, I'm not enough of a haxxor to know what anx of it means. :P
<br>Any more help (on either problem) would be very appreciated. <br><br>Thanks again.<br><br>Walter<br></span>