What is the make.conf file?
Make.conf is portage's and Funtoo's main configuration file. It contains many variables that define how a package will be installed in a Funtoo system. You can customize portage internal variables, such as, portage tree location, sources tarball location, overlays, to name a few. You can customize hardware specs, such as TMPFS, disk limits, GCC compilation flags to achieve best performance, etc. A great deal of this customization is done through the make.conf file. This page will attempt to explain the uses of the make.conf file, different variables that can be added to it, and their uses.
Where is make.conf located?
make.conf is located in
/etc and is a symbolic link to
/etc/portage/make.conf, so these filenames are used interchangeably.
No special tool is required to edit
/etc/portage/make.conf, besides your favorite text editor, of course:
root # nano /etc/portage/make.conf
Portage is very cutomizable. Because of this, many variables are available to configure
/etc/portage/make.conf. Below is an example
make.conf file showing some of the variables that can be used to customize portage. The format of a line of this file is usually
/etc/portage/make.conf- example make.conf variables
CFLAGS="-march=amdfam10 -O2 -pipe" CXXFLAGS="-march=amdfam10 -O2 -pipe" INPUT_DEVICES="evdev" VIDEO_CARDS="vesa nouveau" MAKEOPTS="-j2" USE="mmx sse" ACCEPT_LICENSE="*"
Portage has built-in check for CPU's cores and enables
MAKEOPTS automatically, if not set. In make.conf you may increase or decrease the value, when needed, otherwise it's set to
Below is a list of variables that can be used in
make.conf, along with a description of what they do. For more information on these and other variables, read
Accept All Licenses
/etc/portage/make.conf- accept all licenses
Relocate Source Compile Directory
By default portage unpacks and compiles sources in
/var/tmp/ it appends
portage/pkg-cat/pkg to compile a package elsewhere. For example, if portage compiles a package in
/tmp, it will be built at:
/tmp/portage/pkg-cat/pkg. If you have Funtoo installed on an SSD, it may be a wise decision to mount
/tmp in RAM or on a HDD so that you can minimize the number of writes to your SSD and extend its lifetime. After
/tmp has been mounted off of your SSD, you can tell portage to compile future packages in
/tmp, instead of in
/var/tmp. To do this, add the following line to your
VIDEO_CARDS variable tells portage which video drivers you wish to use on your system. To see the different options that exist for this variable, see Video.
See x11-drivers/xf86-input-synaptics for laptop mice & touch pads.
MAKEOPTS can be used to define how many parallel compilations should occur when you compile a package, which can speed up compilation significantly. By default, this variable is set to the number of cores (or CPU threads) in your system plus one. If for example you have a dual core processor without hyper-threading, then
MAKEOPTS would be set to 3, which could be done manually as follows:
/etc/portage/make.conf- set portage to use 3 threads
If you are unsure about how many processors/threads you have then use /proc/cpuinfo to help you.
(chroot) # grep "processor" /proc/cpuinfo
USE flags define what functionality is enabled when packages are built. It is not recommended to add a lot of them during installation; you should leverage Funtoo Profiles instead as much as possible and only set as needed. A USE flag prefixed with a minus (" - ") sign tells Portage not to use the flag when compiling. Through use flags we generate more secure stripped down binaries with reduced attack surface and better performance. A Funtoo guide to USE flags will be available in the future. For now, you can find out more information about USE flags in the Gentoo Handbook.
Some devices need defined such as x11-drivers/xf86-input-synaptics for touch pads.
/etc/portage/make.conf- synaptics example
Available options can be found on Funtoo Linux Localization.