On 8/8/07, Walter Graf <grafw@xxxxxxxxx> wrote: > On 8/8/07, Bryan DeGrendel <sirnuke@xxxxxxxxx> wrote: > > On 8/7/07, Walter Graf <grafw@xxxxxxxxx> wrote: > > > Hello, all, > > > I'm trying to get Wine running on some Red Hat boxes at my University > (don't > > > worry, I have permission!) ... But, I don't have any root access to the > > > boxes, and I'm limited to installing on my shared (AFS) space. In any > case, > > > I'd probably want it to run from my user space anyways, so that its > > > accessible from all boxes on the network. > > > Some required information, probably: > > > > > > dc3nep68% cat /proc/version > > > Linux version 2.6.9-42.0.10.ELsmp > > > (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version > > > 3.4.6 20060404 (Red Hat 3.4.6-3 )) #1 SMP Fri Feb 16 17:13:42 EST 2007 > > > > > > When I log in, it greets me with: > > > CAEN Red Hat Enterprise Linux WS release 4 (Nahant Update 4) > > > > > > I know, these boxes are pretty old. There's not much I can do about > that. > > > I tried to do an RPM install using --prefix=[somewhere in my AFS user > > > space], but it tells me "wine is not relocatable." (I very well may have > > > done something wrong, as I'm not a RH guy. If anyone has suggestions on > this > > > front, I'd gladly accept them, too!) So, I figured I'd have a go at > > > compiling. So, > > > > > > ./configure --prefix=[a folder in my AFS space] --without-opengl > > > goes fine > > > > > > make depend > > > no problems > > > > > > make > > > goes ok for a bit, then (starting form the topmost error I can find): > > > > > > gcc -m32 -c -I. -I. -I../../include -I../../include > > > > -DINCLUDEDIR="\"/afs/engin.umich.edu/u/g/r/grafw/Private/wine/include/wine\"" > > > > -DDLLDIR="\"/afs/engin.umich.edu/u/g/r/grafw/Private/wine/lib/wine\"" > > > > -DLIBDIR="\"/afs/engin.umich.edu/u/g/r/grafw/Private/wine/lib\"" > > > -DDLLFLAGS="\"-D_REENTRANT -fPIC\"" -DLDDLLFLAGS="\"-shared > > > > -Wl,-Bsymbolic,-z,defs,-init,__wine_spec_init,-fini,__wine_spec_fini\"" > > > -DAS="\"as --32\"" -DCC="\"gcc -m32\"" -DCPP="\"cpp\"" -DCXX="\"g++\"" > > > -DLD="\"ld -m elf_i386\"" > -DPRELINK="\"/usr/sbin/prelink\"" > > > -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement > > > -Wwrite-strings -Wpointer-arith -g -O2 -o winegcc.o winegcc.c > > > cc1: error: invalid option `32"' > > > cc1: error: missing argument to "-m" > > > cc1: error: unrecognized command line option "-f32"" > > > make[2]: *** [ winegcc.o] Error 1 > > > make[2]: Leaving directory > > > > `/afs/engin.umich.edu/u/g/r/grafw/Private/wine-0.9.42/tools/winegcc' > > > make[1]: *** [winegcc] Error 2 > > > make[1]: Leaving directory > > > `/afs/engin.umich.edu/u/g/r/grafw/Private/wine-0.9.42 > > > /tools' > > > make: *** [tools] Error 2 > > > > > > I've tried compiling with several versions of Wine (the exact error > above is > > > from 0.9.42, but I also got the same thing with 0.9.41 an 0.9.12)... > > > That's about it. Does anybody know what's going on here? Do I need to > give > > > any other information? > > > > > > Thanks :D > > > > > > Walter > > > > > > _______________________________________________ > > > wine-users mailing list > > > wine-users@xxxxxxxxxx > > > http://www.winehq.org/mailman/listinfo/wine-users > > > > > > > Hello. I spend some time get a half-decent music player to compile on > > my AFS space a few months ago. A few notes: > > > > 1. I believe all CAEN computers are 64-bit. -m32 flag means compile a > > 32-bit program for a 64-bit OS, if I understand correctly. It looks > > like you need the glibc-devel 32-bit package for that to work [1]. > > 2. There weren't many dev libraries installed on the box I was on. I > > guess if ./configure ran okay there aren't any show stopping problems, > > but you might want to try the --verbose flag to see what you are > > missing. > > > > I don't have any experience with WINE on 64-bit but you might want to > > read this [2] page. > > > > Good luck, > > Bryan DeGrendel > > > > [1] > http://www.redhat.com/archives/fedora-devel-list/2005-January/msg00831.html > > [2] http://wiki.winehq.org/WineOn64bit > > > Thanks for the reply..! > I certainly hadn't considered that these machines were 64 bit.. When > compiling your music player, did you also end up using glibc-devel? How did > you get this working (that is, without root access)? I haven't had any luck > so far. My music player didn't require to be compiled under 32-bit. I did have to install a few libraries to my own home directory to get it to work (the program's configure script allowed me to set the location for each individual library and headers). It was quite a bit of work, and I only managed to get the ncurses UI to work. The music player (Zinf, for the record) is a very simple piece of software. ./configure --help give this: --enable-win64 build a Win64 emulator on AMD64 (won't run Win32 binaries) Which should hopefully get around the lack of 32-bit libraries, at the price only being able to run 64-bit windows software. You could potentially install the glibc-devel-i386 package to your home directory. However, this probably isn't a fairly simple case of setting the include path. Another option is to manually extract the RPM [3]. > And, good call on the ./compile --verbose ... it looks like I'll be missing > quite a few things, but nothing that I really need, I think. I'm currently > only planning on using one program through Wine. > > Thanks again, > > Walter > Sincerely, Bryan DeGrendel [3] http://www.ideaspace.net/users/wkearney/archives/entries/000568.html _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
