Installing Wine

From Wine-Wiki.org
Jump to: navigation, search
This article is part of the HOWTO series.
Installing Wine • Business • Games • Internet • Multimedia • System and Utilities
• Education • Other


Warning: This HOWTO comes with no explicit or implicit warranty whatsoever. Use at you own risk!



This Wiki is Unofficial and relies on suggestions added by visitors like yourself and also contains some comments found in the Wine mailing lists. For the Official Wine Wiki try http://wiki.winehq.org/

Contents

Introduction

Wine can be installed on a variety of systems. People have added how they installed on their version below. Please feel free to add information regarding your distribution

Sometimes getting the very latest wine requires a little work. A user posted wondering why the Wine website advertised a version in its front page which is unavailable for download except as source.

dimesio explained [nov 08 wine user]: Binary packages are the responsibility of the distros [the groups of different Linux distributions]. D. Kegel: feb 09: "Stable version [1] of Wine can usually be installed just like any other Linux application using your package manager. However another noted that not all distributions have updated to the latest stable version (currently 1.01) and J. McKenzie noted this excludes MacOSX. Some updates to the wine download page were suggested in Feb 09 and it may now attempt to detect your distribution and suggest how to install wine.


Further Reading

Advanced Wine Installations and Building from Source

Installing Wine - General Information

Non X86 Processors ARM etc..

Aug 08 wine user In a few months time, a new hand held created by a open source community is going to be released. More specificity Pandora:http://openpandora.org/ Its going to run with the specs: ARM� Cortex-A8 600Mhz+ CPU running Linux [..] will it be possible to recompile wine with ARM support?

Arm has had some work over the last year. Sept 18th 2010 Andre Hentschel posted a patch with the subject: Add ARM support to wine to run winelib apps on ARM devices.

Vitamin: Wine does not emulate CPU. You will not be able to run native windows programs without recompiling them as winelib. http://www.winehq.org/pipermail/wine-devel/2008-August/068098.html

Updating your Wine Install

A user asked [Aug 07 bugzilla 9411] How can we fix old .wine dirs?

A. Julliard:[bug 13113] - There's no need to run wineprefixcreate any more, it's deprecated. Just run wine and everything happens automatically.


It appears best to use Wine as it was intended. Allow it to install to a fake drive_c in your home directory. After Installing Wine, here are some links to get you started:

Dont run Wine with root permissions

Perhaps an experience will help people see why this is a bad idea, because if you run a badly designed program or a program that attempts to do something and is expecting to check the error message, when running as root it may succeed in damaging your system:

Damage to MBR An issue with drive detection software appeared to cause a problem with users who had incorrect privileges on their system, or were (very bravely) running wine as root received quick attention and some patches were quickly added to wine. J. Ernst commented on this in general: If you are not part of the disk group and you are not running as root, this cannot happen. There might be a bug in Wine, but the most important error is people having incorrect rights set or having too much rights. Wine archive

Packaging Wine

P. d'Herbemont [Nov 07?] suggested: It would be great to have a repository which contains everything needed to build the official Wine packages for each distribution.

That would allow have a better transparency on how the maintainers make their packages. Also it means probably a better level of flexibility given that any one could customize its package, and build it with on top of whatever wine version one likes. The package release latency after a Wine release may diminish too. A first step would be to have each maintainer putting in the wiki their howto build the Debian/Ubuntu/... package from scratch. I have in mind what has been done for the Mac OS X package [1]. A second step would be to move spec files, scripts and such to a cvs or git repository like what is in place for the winehq website and documentation.

[1] http://wiki.winehq.org/MacOSX/Building


Links

General Wine Installation Troubleshooting

For more detailed information or for issues specific to your distribution, check the installation guide for your distribution.

LSB

D. Kegel [Aug 06]: LSB, i.e. build once, run everywhere. [...to obtain some feedback for the lsb developers] I downloaded the current LSB SDK from http://www.freestandards.org/en/Download and gave it a shot. [He reported that it currently fails, but hopefully this will change] wine archive

Installing an Older Version of Wine

Older versions of Wine are still available on sourceforge, including rpm's.


Video Drivers

This is a common problem for Wine. Google glxgears to learn about one test you can do.

Ati driver

A user updated his ATI drivers from 8.18.8 to 8.19.10 and reported problems with directx

O. Stieber: ATI drivers have some odd problems with mipmaps that could appear as missing textures, and last week I had a 'new' problem crop up that caused the driver to hang the system, even with old drivers on code that had been in wined3d for months so I'd wouldn't expect any kind of stability with ATI's drivers. [...] I've had some similar reports e.g. http://bugs.winehq.org/show_bug.cgi?id=3779

S. Dosenger: a bug report to ATI, and I hope that they look at it and fix the issue. I think the chances are quite good, the Linux support has really improved over the last months, and they have added support for many things now(Like suspend functionality, which came with the new 8.19.10 driver) Otherwise, I'll try the newest development version of X.org 7.0 ;) wine archive

BSD

While few posts are made in the developer or user forums about the BDS family as few developers make use BSD, they appear happy to support those interested in working on Wine and BSD. [Jun 07 Wine Devel] K. Blin: I'm really happy to provide the Wine side of things for this [Free BSD] bug, but [...] I don't use FreeBSD and my time is limited. [Dec 08 wine devel] K. Blin in reply to the question 'Are bugs on this platform considered valid reportable bugs? I couldn't find any OpenBSD bugs on a quick search in Bugzilla: They are considered valid bugs, but be prepared to go through a lot of iterations if developers aren't able to test on their own machines. (At least I don't have a spare just for toying with OpenBSD) Basically, the best way to get a new, uncommon POSIX OS supported in Wine is to get somebody familiar with (programming on) the OS to work on Wine, or at least closely with the Wine developers. That's how FreeBSD was fixed to better support Wine's needs some time ago. This required a couple of patches to the FreeBSD kernel, IRC, so if the OpenBSD kernel lacks a feature Wine needs, you might have to spend time talking to the OpenBSD team to get features added.


FreeBSD

OpenBSD

NetBSD

Official Links

Apple

Linux

When Building from source, if your distro has binaries, unless you wish to do regression testing, it is usually best that you make use of the prepared binary installations. These often have customizations for their distro. Sometimes the application database recommends using older version of Wine until a serious regression is fixed and Older versions of Wine are still available. If you are building from source see above.

A

C

D

E

F

G

K

L

M

P

Z. Brown jun 08 wine user: it looks like PCLinuxOS has their own version of wine built and ready. It won't be the most recent version but it'll be a working version of wine that you can install with minimal friction. Open the package manager, Synaptic, and search for Wine. For more specifics on this, you'll need to consult either their forums, the linuxquestions.org forums, their mailing lists, or irc. If PCLinuxOS is still building their work off of Mandriva, then you could probably get away with using the Mandriva 2008 binary. No guarantees there.

Z. Brown had made a script for compiling wine [wine user jun 2008] You can find the script for PCLinuxOS 2007 at http://labs.zacbrown.org/doku.php?id=winesourcebuildscripts.

Instructions are on the page as to how to run it. It will require some user input, such as confirming installation of packages via apt-get. Please pay attention to those warnings, especially if its warning you that you could be damaging your system. Let me know how it goes. I've tried the script on two separate installs and it worked flawlessly both times. Note that I'm not doing git check outs for installing. I'll only supply scripts to build the latest release. I'll try and keep it up to date, no later than 2 releases.

R

S

U

W

A developer reported [Oct 06]: I built a set of Wine RPMs for WBEL 3. They should be compatible with RHEL 3 as well. I have not tested them extensively so any feedback would be great. The RPMs are linked from wine archive:

X

Y

Solaris

Retrieved from "http://wine-wiki.org/index.php/Installing_Wine"
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox