-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/16/2011 03:55 PM, DrSuSE wrote: > Ahhh, looks like my issue is that I wasn't building wine-32, I was building 64 and it just wasn't being used and it won't work anyway. > > I cannot seem to get the right combination of magics to build 32bit on my 64bit system, despite having all of the files/etc. > > Aaaaanyway, guess I'll have to hope this works its way into Wine releases. Try something like: https://wiki.archlinux.org/index.php/Install_bundled_32-bit_system_in_Arch64 You'll have to fill in the details of how to install your distribution's 32bit basesystem. Better yet, you could switch to Arch :D Once you have a basesystem installed installed in a chroot jail, get the wine source with like: $ git clone git://source.winehq.org/git/wine.git wine/ Which will put the wine source in your pwd inside the directory "wine"; make sure your chroot has installed your distribution's equivalent of build-essential; then $ cd wine $ CFLAGS="-march=i686 -O2 -fomit-frame-pointer -pipe" \ LDFLAGS="-s" \ ./configure --prefix=/usr --sysconfdir=/etc --verbose; Wait for configure to finish. WINE will tell you which packages it lacks. Some are optional, some are required. You'll have to do a little bit of investigation to make sure your build has support for all the features you want. Next, you can make the package. To speed things up, add the -j flag followed by the number of CPU's you have +1. For instance, for a four core machine: $ make -j 5 Its best to install your package in a isolated path. Make a dir like /home/you/build and then from the source dir, do: $ make DESTDIR=/home/you/build/$( ./wine --version)-$( date +%Y%m%d ) install HOW IT WORKS: The "$( ./wine --version)-$( date +%Y%m%d )" will direct make to make another directory underneath your /home/you/build path that is named after WINE, its version, and the date. From this stage on you could use your distribution's package manager to carry on from this point, or, you can cd to whichever directory "/home/you/build/$( ./wine --version)-$( date +%Y%m%d )" made, and then do: $ tar cf - * | ( cd /; sudo tar xf - ) This installs the package. You can uninstall it again by deleting just the same files in that directory from root. You can get a list of files with something like: $ find * -type f from that directory. When WINE has received more git commits, you can sync your source code by cd'ing to your wine source code directory and: $ git reset --hard origin; git fetch; get rebase origin Then repeat the your build starting from the "./configure" step. Go back to the Arch wiki article and scroll down to read about executing WINE programs (or any 32bit programs inside the chroot) from outside the chroot with the schroot program. Hope this helps, cheers Bryan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNW3d2AAoJEHblvm1J+WqMDFQH/2rwfWtfnoFFS7e+QE8mezZj kw8lUsDqYLQ0mpvkaBeGLNjXdpHHTN6pdfP80uOH6+wjZHIhJMTNAe0kFseS8+dB hcnC90r7s2+k3B5m3kmadVbRdO+TO3k/N721DbCA/16enB6Sni/dzgJ8b3MFl0Um WveD7zdUjB3YZRK49EUcK/RBnKNy1JE9tMOvMl82pxqe/m0usCAUBVRajPqUpNQb D/GyuPcLoxtfw0hioJNa12HM41zA6SUFTTJXmKZyx590GQ5KL1MwjnzyNWwJYG1p fNyIVCY8hLg45ybSi4Oz/nJut00cLYNUDQMaHHJlaT0FSHjL9Qzk2gTYp51MMjo= =cFbC -----END PGP SIGNATURE-----
