[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: New 64-bit Install: Wine



On Monday 11 August 2014 08:36:23 The Wanderer wrote:
> On 08/11/2014 06:27 AM, David Baron wrote:
> > I have no 64-bit .exe's. The few apps I need to run are all fairly
> > old. Seems to be no way to run them.
> > 
> > Wine64 complains about the .exe format. Placing win32:i386 on top of
> > all this complains that the .wine is for a 64bit installation to
> > wine32 will not work. Even if there is no such folder (I purged
> > everything for latest try).
> > 
> > There is apparently no win32:amd64 so the wine32:i386 and a load of
> > 
> > :i386 libs will get installed. Multiarch is great but does not solve
> > 
> > this particular problem.
> 
> I don't have much experience with standalone 64-bit Wine, but my
> solution for 32-bit vs. 64-bit Wine is to build a combined version from
> upstream (git) source - largely because AFAIK Debian does not provide
> any way to get a combined-build Wine installed.
> 
> Unfortunately, while, this used to be relatively straightforward in
> squeeze when we still had an ia32-libs-dev package, it's currently
> broken - and is likely to remain that way until multiarch extends to
> -dev packages, which at this point probably isn't expected to be
> completed (or even necessarily begun) for jessie.
> 
> 
> My "install a newer version of Wine" procedure is currently as follows:
> 
> 1. Update the Wine source.
> 
> 2. In a separate directory (wine64), run the following commands:
>     $(winesrc)/configure --enable-win64
>     make $(make_options)
> 
> 3. In a separate directory (wine32), run the following command:
>     $(winesrc)/configure --with-wine64=$(wine64dir)
> 
> 4. Make note of the errors or "this feature has been disabled" reports
> from the configure run, check the configure log files, identify what
> -dev package(s) need to be installed in order to fix the problem, and
> install the :i386 versions of those packages. (This automatically
> removes the :amd64 versions of the same-dev packages.)
> 
> 5. Repeat steps 3 and 4 until the configure run is successful and all
> the features I want are detected and enabled.
> 
> 6. Run the following commands:
>     make $(make_options)
>     su -c 'make install'
> 
> 7. Back in the wine64 directory, run the following command:
>     su -c 'make install'
> 
> 8. Reinstall all the packages (or at least the -dev packages) which got
> removed in step 4.
> 
> 
> Steps 4, 5 and 8 are highly manual and irritating, such that instead of
> updating Wine monthly, weekly or even daily, I generally update it maybe
> once every three to six months at best. (Building a patched version for
> testing purposes is pretty much off the table entirely.) However, this
> is still the best approach I've found for getting a version of Wine that
> can handle both 32-bit and 64-bit applications in the same install.
> 
> --
>    The Wanderer

While I have compiled wine  before, this is quite a bite!

How about a .deb, maybe on winehq?


Reply to: