Difference between revisions of "Makepkg.conf"

From ArchWiki
Jump to: navigation, search
(CFLAGS by Architecture: remove incomplete, confusing, and outdated list of processor-specific CFLAGS; use -march=native instead)
(See also: fix link)
Line 122: Line 122:
* [[Makepkg]]
* [[Makepkg]]
* [[Kernel Compilation with ABS]]
* [[Kernel Compilation with ABS]]
* [[ArchLinux User-community Repository (AUR)]]
* [[Arch User Repository]]
* [http://en.gentoo-wiki.com/wiki/Safe_Cflags Gentoo Wiki: Safe CFlags]
* [http://en.gentoo-wiki.com/wiki/Safe_Cflags Gentoo Wiki: Safe CFlags]

Revision as of 19:50, 19 March 2010

The file Template:Filename contains configuration options for make, makepkg and gcc. This file is sourced, so you can include any special compiler flags you wish to use (however, only the variables described below are exported to the build environment). These settings are helpful when building for different architectures and optimizations.

Do keep in mind that not all package Makefiles will use your exported variables. Some of them override them in the original Makefiles or the PKGBUILD.

The default file is fairly well commented, so it may be easiest to simply follow directions given there for customization.


DLAGENTS=(protocol::/path/to/command [options] ...)

Sets the download agents used to fetch source files specified with a URL in the PKGBUILD file. Options can be specified for each command as well and the download URL is placed on the end of the command. This is more flexible than the former FTPAGENT variable, as any protocol can have a download agent. Several examples are provided in the default makepkg.conf.


Specifies your computer architecture. Possible values include "i686" or "x86_64", which should have been set automatically during installation.


A string such as "i686-pc-linux-gnu". Do not modify unless you know what you are doing. This can be commented out by most users if desired.


Flags used for the C compiler. This is a key part to the use of makepkg. Usually several options are specified, and the most common string resembles something like this: "-march=i686 -O2 -pipe". Another useful option may be -mcpu in place of -march.


Flags used for the C++ compiler.


This is often used to set the number of jobs used, for example, -j2. Typically, this is modified for SMP systems.

BUILDENV=(fakeroot !distcc color !ccache)

These are the default values for the array that contains options which affect the build environment. All options should always be left in the array. To enable or disable an option, simply remove or place an exclamation symbol (!) at the front of the option. Each works as follows:


Allow building packages as a non-root user. This is highly recommended.


Use the distributed C/C++/ObjC compiler to spread compilation among multiple machines. If this is enabled, DISTCC_HOSTS must be specified as well.


Colorize output messages, making output easier to read.


Use ccache to cache compilation by default. This allows for faster compiles if you are continuously recompiling the same packages. It can be disabled for individual packages by placing !ccache in the PKGBUILD options array.

DISTCC_HOSTS="host1 ..."

If using DistCC, this is used to specify a space-delimited list of hosts running in the DistCC cluster. In addition, you will want to modify your MAKEFLAGS to accomodate the change.

OPTIONS=(strip !docs libtool emptydirs)

These are the default values for the array that contains options which affect the default packaging. All four are equivalent to options that can be placed in the PKGBUILD. All options should always be left in the array; to enable or disable an option simply remove or place an "!" at the front of the option. Each works as follows:


Strip symbols from binaries and libraries. If you frequently use a debugger on programs or libraries, it may be helpful to disable this option.


Save doc and info directories. If you wish to delete doc and info directories, specify !docs in the array.


Leave libtool (.la) files in packages. Specify !libtool to remove them


Leave empty directories in packages


Compress manual (man and info) pages in MAN_DIRS with gzip


Remove files specified by PURGE_TARGETS

INTEGRITY_CHECK=(check1 ...)

File integrity checks to use. Multiple checks may be specified, and they affect both generation and checking. The current valid options are: md5, sha1, sha256, sha384, and sha512.


Manual (man and info) directories to compress (if zipman is specified)

DOC_DIRS=(usr/{,local/}{,share/}{doc,gtk-doc} opt/*/{doc,gtk-doc})

If "!docs" is specified in the OPTIONS array, this variable will instruct makepkg where to look to remove docs. If you build packages that are located in opt/, you may need to add the directory to this array. Note: Do not add the leading slash to the directory name.


If this value is not set, packages will by default be placed in the current directory (location of the PKGBUILD. Many people like to keep all their packages in one place so this option allows this behavior. A common location is "/home/packages".

STRIP_DIRS=(bin lib sbin usr/{bin,lib,sbin,local/{bin,lib,sbin}} opt/*/{bin,lib,sbin})

Directories to be searched for the strip option (if strip is specified)

PURGE_TARGETS=(usr/{,share}/info/dir .packlist *.pod)

Files to be removed from all packages (if purge is specified)


If this value is not set, downloaded source files will only be stored in the current directory. Many people like to keep all source files in a central location for easy cleanup, so this path can be set here.

PACKAGER="John Doe <john@doe.com>"

This value is used when querying a package to see who was the builder. It is recommended you change this to your name and email address.


Do not touch these unless you know what you are doing.


Has an effect on how many jobs are passed for compilation. Generally -j2, plus 1 for each additional CPU/core is the adequate choice. Optimizing for multiple cores can sometimes increase compiling performance, shortening compile times. However, you should be warned that occasionally using anything but the default can cause compilation problems, though many have agreed that -j3 is fairly safe to use for the majority of packages. E.g., for a dual-core CPU:



Arch currently optimizes for i686 and x86-64 architectures. The default makepkg.conf CFLAGS are compatible with all machines within their respective architectures. Further optimizing for CPU type can theoretically enhance performance for packages built with such optimizations, though such gains are most likely not human-perceivable.

As of version 4.3.0, the gcc compiler offers the Template:Codeline switch that enables CPU auto-detection and automatically selects optimizations supported by the local machine at gcc runtime. To use it, just modify the Arch Linux default settings by changing the CFLAGS line as follows:

CFLAGS="-march=native -O2 -pipe"

See the gcc man page for a complete list of available options. The Gentoo Compilation Optimization Guide and Safe Cflags wiki article provide more in-depth information.

i686 default

CFLAGS="-march=i686 -mtune=generic -O2 -pipe"

x86_64 default

CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe"

See also