I am using Ubuntu 11.10 64bit and trying to install wine 1.5, using this method:
Install Wine on Ubuntu:
sudo apt-get install libfreetype6-dev gobject* libxrender-dev libfontconfig-dev pthread* libpthread-stubs0-dev xext* libsm-dev
and copy the following commands in the Terminal:
wget http://prdownloads.sourceforge.net/wine/wine-1.5.0.tar.bz2
tar -xjvf wine-1.5.0.tar.bz2
cd wine-1.5.0
Install some packages:
sudo apt-get install flex bison qt3-dev-tools qt4-qmake
./configure
cd tools
./wineinstall
All goes well, but at the end, I get this error message:
checking for -lfreetype... not found
configure: error: FreeType 32-bit development files not found. Fonts will not be built.
Use the --without-freetype option if you really want this.
Does anyone know how to install lfreetype?
Get to the directory that you've extracted the files for wine.
In terminal, run this command:
Then after it's completely done, run:
It complains about missing the 32bit dev package of freetype.
You can try installing it with
sudo apt-get install libfreetype6-dev:i386
and see if the warning has gone.Revert the following patch from your source tree and compile again:
To configure wine on 64-bit machine, you should do:
If you really want to compile 32-bit wine on 64-bit machine, then I think the easiest way is to use the lxc container as Ubuntu makes building 32-bit wine hard because the 64-bit system doesn't come with a full set of 32-bit development libraries (See: Bug #990982).
So the basic approach to compile both 32-bit and 64-bit wine is:
On the page Building Biarch (Shared WoW64) Wine On Ubuntu we can read the following instructions:
Install the 64-bit prerequisites:
Build 64-bit wine:
Install lxc:
Create a 32-bit container named "my32bitbox" using the Ubuntu template and bind your home directory to the /home directory in the container:
Copy the apt configuration from the host to the lxc container:
Start the container; at the console login prompt it gives you, log in with your username and password.
Now you're inside the container, in your real home directory. If you are not in the container (you do not have the prompt username@my32bitbox), then open a new terminal and:
Now, you are in the container. Do an out-of-tree build of Wine as normal, just to get the tools. You'll have to install all the needed prerequisites first. For instance:
Still inside the container, do it again, this time pointing to the 64-bit build for data, and the 32-bit tools build for tools:
Still inside the container, install the 32-bit wine to force the last little bit of building:
While still inside the container, shut it down:
This drops you back out into your real machine. Next, you need to remove all existing Wine packages. You can do this from the command line but it's probably easier with aptitude or one of the GUI package management tools. You will need wine-mono, wine-gecko, and optionally winetricks for your compiled version of wine. However, these packages may depend on the existing wine installation which may force you to remove them.
Install the newly built wine into your real machine:
Warning: When you install a locally built version of Wine, the package management system will not know it exists since it did not come from a package. Thus it is possible to later break its dependencies or install a conflicting version of wine without a warning from the package management tools. You can prevent this by creating a package or by blocking conflicting packages with apt-pinning by setting "Pin-Priority: -1" for the packages.
Note: Many of the above commands require root privileges. Your user account needs to have access to root via
sudo
or you need to switch to a user account.Linux
The problem is that Ubuntu pkg-config doesn't see your FreeType 32-bit development files.
To verify that this is the case, you can check it by the following command:
You should have the error, that pkg-config can't find this package.
Note: If you don't have pkg-config, please install it via
sudo apt-get install pkg-config
Then, please verify if your freetype was installed correctly and where.
Try to reinstall it, just in case:
If still doesn't work, please find your pc file in your freetype package:
or anywhere else:
and make sure that this file is linked up inside your pkgconfig directory (
locate pkgconfig
):Note: Replace YOUR_FOUND_PATH with your full path of freetype2.pc file.
* If you can't find your pc file, please create one inside your pkc_config dir (as freetype2.pc):
If your problem is still not solved (or it's related to something else), please debug your ./configure script in shell:
And find the place of your problem (e.g. which pkg-config command is executed to verify existence of the specific package).
Mac
If you have similar problem on Mac and you found this topic, please use homebrew to install your freetype package:
If you still have the problem, check this bug.
Just install the default libfreetype6-dev, and libfreetype6:i386, next make a link for the library.
For unknown reason in one of my PCs I had a problem when the configure told an error in libfreetype6, but it actually was libz and libpng. Either way, you can solve the problem the same way
A general way to solve alike problems: open the
config.log
file, goto the end, and search in the upper direction a worderror
. You will find a code that have been used to test a presence of a library or headers. Just copy the main function with includes into a separate file; next seek above the code the command that was used to compile. It would look something likeRemove the
>&5
part, write instead ofconftest.c
name of your test file (to which you just copied the code), and try to compile with this command — you will see a much more useful error messages. That is basically the minimal test case, and once it is solved, the problem solved too.Tips for possible errors:
-dev
postfix, then if it didn't work, with:i386
. If it didn't work again like in the case of the libfreetype, then go with the solution that written above — i.e. make symbolic links by hand.well instead you sudo what you what it's better you just go to Ubuntu software center and get what you want, comes all in one so you don't have to sudo them all just click one thing and everything come in a package, ready to be use...
Try configure with that line. It might be your trying to compile on 64 bit system a 32 bit wine and you will find that configure sometimes checks in wrong place for the libs.
I installed freetype from source http://sourceforge.net/projects/freetype/files/ with