Calculate linux make conf

Отсутствие /etc/make.conf

Отсутствует файл /etc/make.conf, хотя многие руководства на него ссылаются. Зато есть /etc/portage/make.conf/custom. Это одно и тоже или разные файлы? И где, скажем прописано дефолтное значение ACCEPT_KEYWORDS, если у меня нет /etc/make.conf ?

ln -s /etc/portage/make.conf /etc/make.conf

Или просто правь /etc/portage/make.conf

Нет такого, есть /etc/portage/make.conf/custom. Как я понимаю, это тоже самое. Но второй вопрос остается открытым, откуда берется значение переменной (например, ACCEPT_KEYWORDS), если ее нет в этом файле?

Портаж же по дефолту выставляет. emerge —info и смотрим.

всё было и есть

ну, я смотрю на актуальную документацию на сайте calculate

#sudo cast Lautre

и получи warning от portage о дублирующемся make.conf — хитрый план, чо

make.conf должен быть в /etc/portage уже пару лет как. А еще он может быть директорией, да.

Правь /etc/portage/make.conf/custom и не парься

я смотрю на актуальную документацию на сайте calculate

Portage обращается к файлам make.conf. При этом будет проверен как /etc/make.conf, так и /etc/portage/make.conf (если присутствует в системе), причем настройки, содержащиеся в /etc/portage/make.conf, имеют приоритет над настройками из /etc/make.conf.

Отсюда вывод — /etc/make.conf — старое местоположение, оставленное для обратной совместимости. Еще вопросы?

откуда берется значение переменной (например, ACCEPT_KEYWORDS), если ее нет в этом файле

Источник

tolstiyman

четверг, 21 марта 2013 г.

Настройка make.conf

В Gentoo-like дистрибутивах настройки для всех собираемых программ указаны в файле /etc/make.conf. Здесь указаны глобальные флаги компиляции (уровень оптимизации, процессор, набор инструкций процессора, размер кэша и еще всякое), опции для пакетного менеджера, USE-флаги (расширяют или уменьшают функциональность программ), доступные локализации, архитектура ну и еще немного по мелочи.

Здесь я попытаюсь описать максимум полезных опций, по возможности не перегружая ненужной информацией. Впрочем, задача невыполнима — кому-то чего-нибудь не хватит, другому — много лишнего. Приступим.

Содержимое моего /etc/make.conf выглядит приблизительно так:

ACCEPT_LICENSE=»*»
source /var/lib/layman/make.conf
CFLAGS=»-O2 -march=native -pipe -ffast-math»
CXXFLAGS=»$«
MAKEOPTS=»-j3 -s»
EMERGE_DEFAULT_OPTS=»—jobs=2 —load-average=5″
LINGUAS=»en ru ru_RU»
USE=»-cli -libnotify -gimp -ipod -bluetooth -wifi -cups mmx sse sse2 sse3 3dnow 3dnowext mmxext»
VIDEO_CARDS=»vesa nouveau fglrx radeon»
FEATURES=»ccache»
CCACHE_DIR=»/var/tmp/ccache»
CCACHE_SIZE=»3G»
PORTAGE_NICENESS=»15″

Строка ACCEPT_LICENSE=»*» показывает список допустимых лицензий. Здесь звездочка(*) указывает что допустимы любые лицензии — вероятно, наиболее правильный выбор, если вы не заморачиваетесь правильностью свободы софта.

Строку source /var/lib/layman/make.conf не нужно трогать, оставьте как есть.

Следующие две строки задают настройки компиляции программ, использующих компилятор gcc:

CFLAGS=»-O2 -march=native -pipe -ffast-math»
CXXFLAGS=»$«

Первый параметр указывает уровень оптимизации программы. Всего таких уровней существует 5.

-O0 оптимизация отключена

-O(-O1) включает оптимизацию. Компилятор пытается уменьшить размер кода и ускорить работу программы (увеличивается время компиляции).
Активируются следующие флаги (могут использоваться и другие специфичные флаги): -fauto-inc-dec -fcprop-registers -fdce -fdefer-pop -fdelayed-branch -fdse -fguess-branch-probability -fif-conversion2 -fif-conversion -finline-small-functions -fipa-pure-const -fipa-reference -fmerge-constants -fsplit-wide-types -ftree-builtin-call-dce -ftree-ccp -ftree-ch -ftree-copyrename -ftree-dce -ftree-dominator-opts -ftree-dse -ftree-fre -ftree-sra -ftree-ter -funit-at-a-time
-O2 следующий уровень оптимизации. GCC выполняет почти все поддерживемые оптимизации (кроме ускорения выполнения за счет увеличения кода). Не выполняется раскрутка циклов и подстановка функций. Еще больше увеличивается время компиляции и эффективность кода
Активируются все флаги уровня -O1, а также следующие: -fthread-jumps -falign-functions -falign-jumps -falign-loops -falign-labels -fcaller-saves -fcrossjumping -fcse-follow-jumps -fcse-skip-blocks -fdelete-null-pointer-checks -fexpensive-optimizations -fgcse -fgcse-lm -findirect-inlining -foptimize-sibling-calls -fpeephole2 -fregmove -freorder-blocks -freorder-functions -frerun-cse-after-loop -fsched-interblock -fsched-spec -fschedule-insns -fschedule-insns2 -fstrict-aliasing -fstrict-overflow -ftree-switch-conversion -ftree-pre -ftree-vrp

-O3 максимальный уровень оптимизации. Еще немного увеличивает время компиляции и немного повышает эффективность кода, но может быть и обратный эффект — производительность программы может упасть.
Активируются все флаги уровня -O2, а также следующие: -finline-functions -funswitch-loops -fpredictive-commoning -fgcse-after-reload -ftree-vectorize

-Os оптимизация по размеру. Компилятор пытается уменьшить размер кода. Активируются в основном те флаги из -O2, которые не увеличивают размер выходного файла.
Отключаются следующие флаги: -falign-functions -falign-jumps -falign-loops -falign-labels -freorder-blocks -freorder-blocks-and-partition -fprefetch-loop-arrays -ftree-vect-loop-version

-Ofast еще один уровень оптимизации, добавленный в gcc >= 4.6. Как следует из названия, служит для ускорения работы программ.
Активируются все флаги из -O3, а также флаг -ffast-math.

Флаг -ffast-math разрешает компилятору нарушать некоторые ANSI или IEEE правила и/или спецификации в интересах оптимизации кода по скорости выполнения (например, предполагать что параметры функции sqrt — неотрицательные числа). Следует учитывать, что некоторые пакеты могут с этой опцией не собраться.

Флаг -march позволяет оптимизировать код под определенный процессор. Значение флага native предписывает компилятору автоматически определить семейство процессоров — на данном этапе, вероятно, наиболее разумный выбор. Здесь можно указать семейство явно, а можно испльзуя еще десяток-другой флагов вручную настроить процессор более тонко (размер кэшей, наборы инструкций и т. п.), но это потребует на уровень более глубокого погружения в изучение опций компилятора.

Флаг -pipe заставляет компилятор передавать промежуточные данные через конвеер в оперативной памяти (разгружает HDD). Вобщем, нужна почти всегда.

Есть в указании флагов компиляции и свои правила:
— если флаги противоречат друг другу, то силу имеет флаг указанный последним;
— опции, начинающиеся с -f, -m, -W можно отключить, добавив префикс no- (например, если есть флаг -f(опция), то отключить его можно так -fno-(опция)).

Строка MAKEOPTS=»-j3 -s» задает опции команды make:
-j3 — задает количество запускаемых копий make, рекомендуемое значение количество_процессоров(ядер, потоков)+1 или удвоенное_количество_процессоров(ядер, потоков)+1;
-s — уменьшает количество информации, выводимой make — немного ускоряет сборку.

Строка EMERGE_DEFAULT_OPTS=»—jobs=2 —load-average=8″ задает опции для менеджера пакетов:
—jobs=2 — количество одновременно собираемых пакетов, ведь часто встречаются пакеты, которые собираются в один поток (вероятно, должен равняться количеству процессоров);
—load-average=5 — число блокирующих процессов в очереди на исполнение (блокирующий процесс — процесс, ожидающий ресурсов (процессор, дисковая подсистема ввода/вывода, сеть) для продолжения работы; соответственно параметр — это максимальное значение при котором emerge будет запускать дополнительные процессы. Параметр не до конца познан — находится в процессе познания. Система может виснуть при 3 и нормально/удовлетворительно работать при 8.

Строка LINGUAS=»en ru ru_RU» понятна и описывает доступные локализации. ru_RU нужет для smplayer (может еще для чего), иначе он не знает русского.

Строка USE=»-cli -libnotify -gimp -ipod -bluetooth -wifi -cups mmx sse sse2 sse3 3dnow 3dnowext mmxext» — так называемые USE-флаги («-» отключает флаг, без минуса — флаг включен). Они нужны для управления зависимостями и уменьшают/расширяют функциональность приложений:
— флаги «-cli» и «-libnotify» — это попытка настроить шрифты, отдельная большая тема (следует заметить, что в Calculate со шрифтами все нормально, но неправильно отображаются некоторые pdf файлы — в основном сервис мануалы и даташиты на какие нибудь микрухи, хотя проще установить acroreader);
— флаги «-gimp -ipod -bluetooth -wifi -cups» отключают то, что написано — я не пользуюсь GIMP, iPod, у меня нет bluetooth и wi-fi, нет принтера (по идее отвалится также экспорт в pdf, например в libreoffice);
— флаги «mmx sse sse2 sse3 3dnow 3dnowext mmxext» — это наборы инструкций, наличествующие в моем процессоре.
USE-флагов много и все для чего-нибудь нужны — непаханое поле для настройки. Можно также указывать USE-флаги отдельно для пакета, но не здесь.

Строка VIDEO_CARDS=»vesa nouveau fglrx radeon» доступные драйвера видеокарт. Скажем, если у вас встроенное видео intel, то вам не нужны драйвера для карт nvidia и AMD. Здесь:
— vesa — универсальный драйвер для почти любой видеокарты — медленный но должен работать почти везде;
— nouveau — свободный драйвер для видеокарт nvidia, разрабатывается сообщесвом, не поддерживает 3D (есть еще проприетарый драйвер — там работает все и вроде бы нормально/удовлетворительно) — держу для встроенного в материнскую плату видео;
— fglrx — проприетарный драйвер для карт AMD/ATI, работает нормально, но косяки присутствуют;
— radeon — свободный драйвер для карт AMD/ATI, разрабатывается сообществом, поддержка 3D хреновая.

Для ускорения компиляции можно использовать программу ccache. Она прилично ускоряет обновление, установку программ и полную пересборку системы в случае совпадения исходного кода при повторной компиляции, что происходит в большинстве случаев, так как обычно даже в новых пакетах достаточно много не измененного исходного кода. Для этого добавлены следующие строки:

Для начала программу ccache нужно установить:

Строка CCACHE_SIZE=»3G» устанавливает размер кэша программы — обычно достаточно 2 ГБ, по умолчанию установлено 1 ГБ.

Для просмотра статистики кэша компиляции можно воспользоваться командой:

# CCACHE_DIR=»/var/tmp/ccache» ccache -s
Строка PORTAGE_NICENESS=»15″ указывает с каким приоритетом должен запускаться emerge — это т. н. фактор уступчивости, чем он выше тем ниже приоритет процесса (выше уступчивость). Диапазон параметра от -20 до 19. Обычно программы запускаются с фактром уступчивости равным нулю (такая себе золотая середина), но emerge в процессе компиляции пакетов может нехило подвешивать систему, поэтому было нагуглено значение 15.

Источник

make.conf¶

make.conf — custom settings for Portage

SYNOPSIS¶

/etc/make.conf and /etc/portage/make.conf

DESCRIPTION¶

This file contains various variables that are used by Portage . Portage will check the currently-defined environment variables first for any settings. If no environment settings are found, Portage then checks the make.conf files. Both /etc/make.conf and /etc/portage/make.conf are checked (if present), and settings from /etc/portage/make.conf will override settings from /etc/make.conf . If no setting is found in the make.conf files, Portage checks make.globals . If no setting is found there, the profile’s default setting is grabbed from /etc/make.profile/make.defaults . Please note that all user settings should be made in the environment or in the make.conf files, which are intended to be customized by the user. Exceptions are incremental variables such as USE flags, CONFIG_PROTECT* , and ACCEPT_KEYWORDS . Incremental variables are propagated down from make.defaults to make.globals to make.conf to the environment settings. Clearing these variables requires a clear-all as in: export USE=»-*» In order to create per-package environment settings, refer to package.env in portage(5).

VARIABLES¶

ACCEPT_CHOSTS = [space delimited list of CHOST values] ¶

Specifies acceptable CHOST values. Regular expression syntax is supported, so it is necessary to escape CHOST characters if they have special meaning in regular expressions.
Defaults to the value of $CHOST .

ACCEPT_KEYWORDS = [space delimited list of KEYWORDS] ¶

Enable testing of ebuilds that have not yet been deemed ‘stable’. Users of the ‘x86’ architecture would set this to ‘

x86′ while ‘amd64’ users would set this to ‘

amd64′ . This is an incremental variable. Only define a

arch .
Defaults to the value of $ARCH .

ACCEPT_LICENSE = [space delimited list of licenses or groups] ¶

This variable is used to mask packages based on licensing restrictions. It may contain both license and group names, where group names are prefixed with the @ symbol. License groups are defined in the license_groups file (see portage(5)). In addition to license and group names, the * and -* wildcard tokens are also supported. Refer to GLEP 23 for further information: http://www.gentoo.org/proj/en/glep/glep-0023.html .
Defaults to the value of * -@EULA .

Examples:¶

# Accept any license

ACCEPT_LICENSE=»*» ¶

# Accept any license except the » public-domain » license

ACCEPT_LICENSE=»* -public-domain» ¶

# Only accept licenses in the FSF-APPROVED license group

ACCEPT_LICENSE=» — * @FSF-APPROVED» ¶

ACCEPT_PROPERTIES = [space delimited list of properties] ¶

This variable is used to mask packages based on PROPERTIES restrictions. In addition to property names, the * and -* wildcard tokens are also supported. This variable can be temporarily overridden using the —accept-properties option of emerge(1). See ebuild(5) for more information about PROPERTIES .
Defaults to the value of * .

Examples:¶

# Accept any properties

ACCEPT_PROPERTIES=»*» ¶

# Accept any properties except the » interactive » property

ACCEPT_PROPERTIES=»* -interactive» ¶

CBUILD ¶

This variable is passed by the ebuild scripts to the configure as —build=$ only if it is defined. Do not set this yourself unless you know what you are doing.

CCACHE_DIR = [path] ¶

Defines the location of the ccache working directory. See the ccache(1) man page for more information.
Defaults to /var/tmp/ccache

CCACHE_SIZE = «size» ¶

This controls the space use limitations for ccache . The default is 2 gigabytes (‘2G’) . Sizes are specified with ‘G’ , ‘M’ , and ‘K’ .

CFLAGS CXXFLAGS ¶

Use these variables to set the desired optimization/CPU instruction settings for applications that you compile. These two variables are passed to the C and C++ compilers, respectively. (CXX is used to refer to the C++ compiler within many buildsystems.) Nearly all ebuild files will take advantage of your custom settings, resulting in a Gentoo Linux that is fully customized to your specifications. Please use sane settings as some packages will fail to compile/run if the optimizations are too extreme.

For more information, see the Invoking GCC section of the gcc manual:
http://gcc.gnu.org/onlinedocs/

CHOST ¶

This variable is passed by the ebuild scripts to the configure step as —host=$ .This way you can force the build-host.

CLEAN_DELAY = integer ¶

Determines how long the countdown delay will be after running ’emerge —unmerge’.
Defaults to 5 seconds.

COLLISION_IGNORE = [space delimited list of files and/or directories] ¶

This variable allows the user to disable collision-protect and protect-owned for specific files and/or directories.
Defaults to /lib/modules .

CONFIG_PROTECT = [space delimited list of files and/or directories] ¶

All files and/or directories that are defined here will have «config file protection» enabled for them. See the CONFIGURATION FILES section of emerge(1) for more information.

CONFIG_PROTECT_MASK = [space delimited list of files and/or directories] ¶

All files and/or directories that are defined here will have «config file protection» disabled for them. See the CONFIGURATION FILES section of emerge(1) for more information.

CTARGET ¶

This variable is passed by the ebuild scripts to the configure as —target=$ only if it is defined.

DISTDIR = [path] ¶

Defines the location of your local source file repository. After packages are built, it is safe to remove any and all files from this directory since they will be automatically fetched on demand for a given build. If you would like to selectively prune obsolete files from this directory, see eclean(1) from the gentoolkit package. Use the PORTAGE_RO_DISTDIRS variable to specify one or more read-only directories containing distfiles . Note that locations under /usr/portage are not necessarily safe for data storage. See the PORTDIR documentation for more information.
Defaults to /usr/portage/distfiles .

DOC_SYMLINKS_DIR ¶

If this variable contains a directory then symlinks to HTML documentation will be installed into it.

EBEEP_IGNORE ¶

Defines whether or not to ignore audible beeps when displaying important informational messages. This variable is unset by default.

EMERGE_DEFAULT_OPTS ¶

Options to append to the end of the emerge (1) command line on every invocation. These options will not be appended to the command line if —ignore-default-opts is specified.

EMERGE_LOG_DIR ¶

Controls the location of emerge.log and emerge-fetch.log .
Defaults to /var/log .

EPAUSE_IGNORE ¶

Defines whether or not to ignore short pauses that occur when displaying important informational messages. This variable is unset by default. If it is set to any value pauses are ignored.

EXTRA_ECONF = [configure options string] ¶

Contains additional options that econf will append to configure script arguments (see ebuild(5)).

FEATURES = «sandbox» ¶

Defines actions portage takes by default. This is an incremental variable. Most of these settings are for developer use, but some are available to non-developers as well. The sandbox feature is very important and should not be disabled by default.

assume-digests ¶

When commiting work to cvs with repoman(1), assume that all existing SRC_URI digests are correct. This feature also affects digest generation via ebuild(1) and emerge(1) ( emerge generates digests only when the digest feature is enabled). Existing digests for files that do not exist in $ will be automatically assumed even when assume-digests is not enabled. If a file exists in $ but its size does not match the existing digest, the digest will be regenerated regardless of whether or not assume-digests is enabled. The ebuild(1) digest command has a —force option that can be used to force regeneration of digests.

binpkg-logs ¶

Keep logs from successful binary package merges. This is relevant only when PORT_LOGDIR is set.

buildpkg ¶

Binary packages will be created for all packages that are merged. Also see quickpkg(1) and emerge(1) —buildpkg and —buildpkgonly options.

buildsyspkg ¶

Build binary packages for just packages in the system set.

candy ¶

Enable a special progress indicator when emerge(1) is calculating dependencies.

ccache ¶

Enable portage support for the ccache package. If the ccache dir is not present in the user’s environment, then portage will default to $/ccache .

*** WARNING *** WARNING » >¶

This feature is known to cause numerous compilation failures. Sometimes ccache will retain stale code objects or corrupted files, which can lead to packages that cannot be emerged. If this happens (if you receive errors like «File not recognized: File truncated»), try recompiling the application with ccache disabled before reporting a bug. Unless you are doing development work, do not enable ccache .

collision-protect ¶

A QA -feature to ensure that a package does not overwrite files it does not own. The COLLISION_IGNORE variable can be used to selectively disable this feature. Also see the related protect-owned feature.

compress-build-logs ¶

The causes all build logs to be compressed while they are being written. Log file names have an extension that is appropriate for the compression type. Currently, only gzip(1) compression is supported, so build logs will have a .gz extension when this feature is enabled.

digest ¶

Autogenerate digests for packages when running the emerge(1), ebuild(1), or repoman(1) commands. If the assume-digests feature is also enabled then existing SRC_URI digests will be reused whenever they are available.

distcc ¶

Enable portage support for the distcc package.

distlocks ¶

Portage uses lockfiles to ensure competing instances do not clobber each other’s files. This feature is enabled by default but may cause heartache on less intelligent remote filesystems like NFSv2 and some strangely configured Samba server ( oplocks off , NFS re-export ). A tool /usr/lib/portage/bin/clean_locks exists to help handle lock issues when a problem arises (normally due to a crash or disconnect).

fakeroot ¶

Enable fakeroot for the install and package phases when a non-root user runs the ebuild(1) command.

fail-clean ¶

Clean up temporary files after a build failure. This is particularly useful if you have PORTAGE_TMPDIR on tmpfs . If this feature is enabled, you probably also want to enable PORT_LOGDIR in order to save the build log. Both the ebuild(1) command and the noclean feature cause the fail-clean feature to be automatically disabled.

fixpackages ¶

Runs the script that will fix the dependencies in all binary packages. This is run whenever packages are moved around in the portage tree. Please note that this can take a lot of time.

getbinpkg ¶

Force emerge to always try to fetch files from the PORTAGE_BINHOST . See make.conf(5) for more information.

installsources ¶

Install source code into /usr/src/debug/$/$ (also see splitdebug ). This feature works only if debugedit is installed and CFLAGS is set to include debug information (such as with the -ggdb flag).

keeptemp ¶

Do not delete the $ directory after the merge process.

keepwork ¶

Do not delete the $ directory after the merge process. $ can then be reused since this feature disables most of the clean phase that runs prior to each build. Due to lack of proper cleanup, this feature can interfere with normal emerge operation and therefore it should not be left enabled for more than a short period of time.

fixlafiles ¶

Modifies .la files to not include other .la files and some other fixes (order of flags, duplicated entries, . )

lmirror ¶

When mirror is enabled in FEATURES , fetch files even when mirror is also in the ebuild(5) RESTRICT variable. Do not use lmirror for clients that need to override RESTRICT when fetching from a local mirror, but instead use a «local» mirror setting in /etc/portage/mirrors , as described in portage(5).

metadata-transfer ¶

Automatically perform a metadata transfer when ’emerge —sync’ is run. In versions of portage >=2.1.5, this feature is disabled by default. When metadata-transfer is disabled, metadata cache from the $/metadata/cache/ directory will be used directly (if available) and eclasses in $/eclass/ must not be modified except by ’emerge —sync’ operations since the cache validation mechanism will not recognize eclass modifications. Normally, this issue only pertains to users of the rsync tree since the cvs tree does not contain a metadata/cache/ directory. Users of the rsync tree who want to modify eclasses should use PORTDIR_OVERLAY in order for the cache validation mechanism to work correctly.

mirror ¶

Fetch everything in SRC_URI regardless of USE settings, except do not fetch anything when mirror is in RESTRICT .

multilib-strict ¶

Many Makefiles assume that their libraries should go to /usr/lib , or $(prefix)/lib . This assumption can cause a serious mess if /usr/lib is not a symlink to /usr/lib64 . To find the bad packages, we have a portage feature called multilib-strict . It will prevent emerge from putting 64bit libraries into anything other than (/usr)/lib64 .

noauto ¶

When utilizing ebuild(1), only run the function requested.

noclean ¶

Do not delete the the source and temporary files after the merge process.

nodoc ¶

Do not install doc files ( /usr/share/doc ).

noinfo ¶

Do not install info pages.

noman ¶

Do not install manpages.

nostrip ¶

Prevents the stripping of binaries that are merged to the live filesystem.

notitles ¶

Disables xterm titlebar updates (which contains status info).

parallel-fetch ¶

Fetch in the background while compiling. Run tail -f /var/log/emerge-fetch.log in a terminal to view parallel-fetch progress.

parse-eapi-ebuild-head ¶

Parse EAPI from the head of the ebuild (first 30 lines). This feature is only intended for experimental purposes and should not be enabled under normal circumstances.

prelink-checksums ¶

If prelink(8) is installed then use it to undo any prelinks on files before computing checksums for merge and unmerge. This feature is useful only if prelink(8) is installed and accurate checksums (despite prelinking) are needed for some reason such as for checking the integrity of installed files or because the unmerge-orphans feature is disabled.

preserve-libs ¶

Preserve libraries when the sonames change during upgrade or downgrade. Libraries are preserved only if consumers of those libraries are detected.

protect-owned ¶

This is identical to the collision-protect feature except that files may be overwritten if they are not explicitly listed in the contents of a currently installed package. This is particularly useful on systems that have lots of orphan files that have been left behind by older versions of portage that did not support the unmerge-orphans feature. Like collision-protect , the COLLISION_IGNORE variable can be used to selectively disable this feature. It is recommended to leave either protect-owned or collision-protect enabled at all times, since otherwise file collisions between packages may result in files being overwritten or uninstalled at inappropriate times. If collision-protect is enabled then it takes precedence over protect-owned .

python-trace ¶

Output a verbose trace of python execution to stderr when a command’s —debug option is enabled.

sandbox ¶

Enable sandbox -ing when running emerge(1) and ebuild(1).

sesandbox ¶

Enable SELinux sandbox -ing. Do not toggle this FEATURE yourself.

severe ¶

When checking Manifests, only accept ones that have been signed by a key which you trust.

sfperms ¶

Stands for Smart Filesystem Permissions. Before merging packages to the live filesystem, automatically search for and set permissions on setuid and setgid files. Files that are setuid have the group and other read bits removed while files that are setgid have the other read bit removed. See also suidctl below.

When commiting work to cvs with repoman(1), sign the Manifest with a GPG key. Read about the PORTAGE_GPG_KEY variable in make.conf(5).

skiprocheck ¶

Skip write access checks on DISTDIR when fetching files. This is useful when FETCHCOMMAND and RESUMECOMMAND are used to forward fetch requests to a server that exposes DISTDIR as a read-only NFS share. A read-only DISTDIR is not compatible with the distlocks , so it is recommended to also add «-distlocks» to FEATURES in order to avoid warning messages that are triggered by this incompatibility.

split-elog ¶

Store logs created by PORTAGE_ELOG_SYSTEM = «save» in category subdirectories of PORT_LOGDIR/elog , instead of using PORT_LOGDIR/elog directly.

split-log ¶

Store build logs in category subdirectories of PORT_LOGDIR/build , instead of using PORT_LOGDIR directly.

splitdebug ¶

Prior to stripping ELF etdyn and etexec files, the debugging info is stored for later use by various debuggers. This feature is disabled by nostrip . For installation of source code, see installsources .

strict ¶

Have portage react strongly to conditions that have the potential to be dangerous (like missing or incorrect digests for ebuilds ).

stricter ¶

Have portage react strongly to conditions that may conflict with system security provisions (for example textrels , executable stack). Read about the QA_STRICT_* variables in make.conf(5).

suidctl ¶

Before merging packages to the live filesystem, automatically strip setuid bits from any file that is not listed in /etc/portage/suidctl.conf .

Run package-specific tests during each merge to help make sure the package compiled properly. See test in ebuild(1) and src_test() in ebuild(5). This feature implies the «test» USE flag.

test-fail-continue ¶

If «test» is enabled FEATURES and the test phase of an ebuild fails, continue to execute the remaining phases as if the failure had not occurred. Note that the test phase for a specific package may be disabled by masking the «test» USE flag in package.use.mask (see portage(5)).

unmerge-logs ¶

Keep logs from successful unmerge phases. This is relevant only when PORT_LOGDIR is set.

unmerge-orphans ¶

If a file is not claimed by another package in the same slot and it is not protected by CONFIG_PROTECT , unmerge it even if the modification time or checksum differs from the file that was originally installed.

unknown-features-filter ¶

Filter out any unknown values that the FEATURES variable contains.

unknown-features-warn ¶

Warn if FEATURES contains one or more unknown values.

userfetch ¶

When portage is run as root, drop privileges to portage : portage during the fetching of package sources.

userpriv ¶

Allow portage to drop root privileges and compile packages as portage : portage without a sandbox (unless usersandbox is also used).

usersandbox ¶

Enable the sandbox in the compile phase, when running without root privileges ( userpriv ).

usersync ¶

Drop privileges to the owner of PORTDIR for emerge(1) —sync operations.

webrsync-gpg ¶

Enable GPG verification when using ’emerge-webrsync’.

FETCHCOMMAND ¶

This variable contains the command used for fetching package sources from the internet. It must contain the full path to the executable as well as the place-holders \$ , \$ and \$ . The command should be written to place the fetched file at \$/\$ . Also see RESUMECOMMAND .

FFLAGS FCFLAGS ¶

Use these variables to set the desired optimization/CPU instruction settings for applications that you compile with a FORTRAN compiler. FFLAGS is usually passed to the FORTRAN 77 compiler, and FCFLAGS to any FORTRAN compiler in more modern build systems.

For more information, see the Invoking GCC section of the gcc manual:
http://gcc.gnu.org/onlinedocs/

GENTOO_MIRRORS = [ URIs ]¶

Insert your space-separated list of local mirrors here. These locations are used to download files before the ones listed in the ebuild scripts. Merging mirrorselect can help. Entries in this variable that have no protocol and simply start with a ‘/’ path separator may be used to specify mounted filesystem mirrors.

http_proxy ftp_proxy = [protocol://host:port] ¶

These vars are used if the sources must be downloaded from the internet by wget(1). They are only required if you use a proxy server for internet access.

INSTALL_MASK = [space delimited list of file names] ¶

Use this variable if you want to selectively prevent certain files from being copied into your file system tree. This does not work on symlinks, but only on actual files. Useful if you wish to filter out files like HACKING.gz and TODO.gz . The INSTALL_MASK is processed just before a package is merged. Also supported is a PKG_INSTALL_MASK variable that behaves exactly like INSTALL_MASK except that it is processed just before creation of a binary package.

LDFLAGS ¶

A list of flags to pass to the compiler when the linker will be called. See ld(1) for linker flags, but do not forget that these flags will be passed directly to the compiler. Thus, you must use ‘-Wl’ to escape the flags which only the linker understands (see gcc(1)).

*** WARNING *** WARNING » >¶

Setting this and other *FLAGS variables arbitrarily may cause compile or runtime failures. Bug reports submitted when nonstandard values are enabled for these flags may be closed as INVALID.

MAKEOPTS ¶

Use this variable if you want to use parallel make. For example, if you have a dual-processor system, set this variable to «-j2» or «-j3» for enhanced build performance with many packages. Suggested settings are between CPUs+1 and 2*CPUs+1 . In order to avoid excess load, the —load-average option is recommended. For more information, see make(1). Also see emerge(1) for information about analogous —jobs and —load-average options.

NOCOLOR = [«true» | «false»] ¶

Defines if color should be disabled by default.
Defaults to «false» .

PKGDIR = [path] ¶

Defines the location where created .tbz2 binary packages will be stored when the emerge(1) —buildpkg option is enabled. By default, a given package is stored in a subdirectory corresponding to its category. However, for backward compatibility with the layout used by older versions of portage , if the $/All directory exists then all packages will be stored inside of it and symlinks to the packages will be created in the category subdirectories. Note that locations under /usr/portage are not necessarily safe for data storage. See the PORTDIR documentation for more information.
Defaults to /usr/portage/packages .

PORT_LOGDIR ¶

This variable defines the directory in which per-ebuild logs are kept. Logs are created only when this is set. They are stored as $:$:YYYYMMDD-HHMMSS.log in the directory specified. If the directory does not exist, it will be created automatically and group permissions will be applied to it. If the directory already exists, portage will not modify it’s permissions.

PORTAGE_BINHOST = [space delimited URI list] ¶

This is a list of hosts from which portage will grab prebuilt-binary packages. Each entry in the list must specify the full address of a directory serving tbz2s for your system. This is only used when running with the get binary PKG options are given to emerge . Review emerge(1) for more information. For versions of portage less that 2.1.6, this variable should point to the ‘All’ directory on the host that creates the binary packages and not to the root of the PKGDIR . Starting with portage 2.1.6, it should point to a directory containing a ‘Packages’ index file. If $/Packages does not exist then portage will attempt to use the older protocol.

PORTAGE_BINHOST_HEADER_URI = «ftp://login:pass@grp.mirror.site/pub/grp/i686/athlon-xp/» ¶

This variable only makes sense on a system that will serve as a binhost and build packages for clients. It defines the URI header field for the package index file which is located at $/Packages . Clients that have PORTAGE_BINHOST properly configured will be able to fetch the index and use the URI header field as a base URI for fetching binary packages. If the URI header field is not defined then the client will use its $ setting as the base URI .

PORTAGE_BINPKG_TAR_OPTS ¶

This variable contains options to be passed to the tar command for creation of binary packages.

PORTAGE_BUNZIP2_COMMAND = [bunzip2 command string] ¶

This variable should contain a command that is suitable for portage to call for bunzip2 extraction operations.

PORTAGE_BZIP2_COMMAND = [bzip2 command string] ¶

This variable should contain a command that is suitable for portage to call for bzip2 compression operations. PORTAGE_BZIP2_COMMAND will also be called for extraction operation, with -d appended, unless the PORTAGE_BUNZIP2_COMMAND variable is set.

PORTAGE_COMPRESS = «bzip2» ¶

This variable contains the command used to compress documentation during the install phase.

PORTAGE_COMPRESS_FLAGS = «-9» ¶

This variable contains flags for the PORTAGE_COMPRESS command.

PORTAGE_COMPRESS_EXCLUDE_SUFFIXES = «gif htm[l]? jp[e]?g pdf png» ¶

This variable contains a space delimited list of file suffixes for which matching files are excluded when the PORTAGE_COMPRESS command is called. Regular expressions are supported and the match is performed only against the portion of the file name which follows the last period character.

PORTAGE_ELOG_CLASSES ¶

PORTAGE_ELOG_SYSTEM ¶

PORTAGE_ELOG_COMMAND ¶

PORTAGE_ELOG_MAILURI ¶

PORTAGE_ELOG_MAILFROM ¶

PORTAGE_ELOG_MAILSUBJECT ¶

Please see /usr/share/portage/config/make.conf.example for elog documentation.

PORTAGE_FETCH_CHECKSUM_TRY_MIRRORS = 5 ¶

Number of mirrors to try when a downloaded file has an incorrect checksum.

PORTAGE_FETCH_RESUME_MIN_SIZE = 350K ¶

Minimum size of existing file for RESUMECOMMAND to be called. Files smaller than this size will be removed and FETCHCOMMAND will be called to download the file from the beginning. This is useful for helping to ensure that small garbage files such as HTML 404 pages are properly discarded. The variable should contain an integer number of bytes and may have a suffix such as K , M , or G .

PORTAGE_GPG_DIR ¶

The gpg(1) home directory that is used by repoman(1) when sign is in FEATURES .
Defaults to $HOME/.gnupg .

PORTAGE_GPG_KEY ¶

The gpg(1) key used by repoman(1) to sign manifests when sign is in FEATURES .

PORTAGE_IONICE_COMMAND = [ionice command string] ¶

This variable should contain a command for portage to call in order to adjust the io priority of portage and its subprocesses. The command string should contain a \$ place-holder that will be substituted with an integer PID . For example, a value of «ionice -c 3 -p \$» will set idle io priority. For more information about ionice , see ionice(1). This variable is unset by default.

PORTAGE_NICENESS = [number] ¶

The value of this variable will be added to the current nice level that emerge is running at. In other words, this will not set the nice level, it will increment it. For more information about nice levels and what are acceptable ranges, see nice(1).

PORTAGE_RO_DISTDIRS = [space delimited list of directories] ¶

When a given file does not exist in DISTDIR , search for the file in this list of directories. Search order is from left to right. Note that the current implementation works by creating a symlink inside DISTDIR , but that may change in the future.

PORTAGE_RSYNC_INITIAL_TIMEOUT = integer ¶

Used by ’emerge —sync’ as a timeout for the initial connection to an rsync server.
Defaults to 15 seconds.

PORTAGE_RSYNC_EXTRA_OPTS = [rsync options string] ¶

Additional rsync options to be used by ’emerge —sync’.
Defaults to no value.

PORTAGE_RSYNC_OPTS = [rsync options string] ¶

Default rsync options to be used by ’emerge —sync’. Do not change this unless you know exactly what you are doing! Defaults to » —recursive —links —safe-links —perms —times —compress —force —whole-file —delete —stats —timeout=180 —exclude=’/distfiles’ —exclude=’/local’ —exclude=’/packages’ «

PORTAGE_RSYNC_RETRIES = [NUMBER] ¶

The number of times rsync should retry on failed connections before giving up. If set to a negative number, then retry until all possible addresses are exhausted.
Defaults to -1 .

PORTAGE_SYNC_STALE = [NUMBER] ¶

Defines the number of days after the last ’emerge —sync’ that a warning message should be produced. A value of 0 will disable warnings.
Defaults to 30 .

PORTAGE_TMPDIR = [path] ¶

Defines the location of the temporary build directories.
Defaults to /var/tmp .

PORTAGE_WORKDIR_MODE = «0700» ¶

This variable controls permissions for WORKDIR (see ebuild(5)).

PORTDIR = [path] ¶

Defines the location of the Portage tree. This is the repository for all profile information as well as all ebuilds . If you change this, you must update your /etc/make.profile symlink accordingly.
Defaults to /usr/portage .

*** WARNING *** WARNING » >¶

Data stored inside PORTDIR is in peril of being overwritten or deleted by the ’emerge —sync’ command. The default value of PORTAGE_RSYNC_OPTS will protect the default locations of DISTDIR and PKGDIR , but users are warned that any other locations inside PORTDIR are not necessarily safe for data storage. You should not put other data (such as overlays) in your PORTDIR . Portage will walk directory structures and may arbitrary add invalid categories as packages.

PORTDIR_OVERLAY = «[path] [different_path] [etc. ]» ¶

Defines the directories in which user made ebuilds may be stored and not overwriten when ’emerge —sync’ is run. This is a space delimited list of directories.
Defaults to no value.

QA_STRICT_EXECSTACK = «set» ¶

Set this to cause portage to ignore any QA_EXECSTACK override settings from ebuilds . See also ebuild(5).

QA_STRICT_WX_LOAD = «set» ¶

Set this to cause portage to ignore any QA_WX_LOAD override settings from ebuilds . See also ebuild(5).

QA_STRICT_TEXTRELS = «set» ¶

Set this to cause portage to ignore any QA_TEXTREL override settings from ebuilds . See also ebuild(5).

QA_STRICT_DT_HASH = «set» ¶

Set this to cause portage to ignore any QA_DT_HASH override settings from ebuilds . See also ebuild(5).

QA_STRICT_PRESTRIPPED = «set» ¶

Set this to cause portage to ignore any QA_PRESTRIPPED override settings from ebuilds . See also ebuild(5).

RESUMECOMMAND ¶

This variable contains the command used for resuming package sources that have been partially downloaded. It should be defined using the same format as FETCHCOMMAND , and must include any additional option(s) that may be necessary in order to continue a partially downloaded file located at \$/\$ .

ROOT = [path] ¶

Use ROOT to specify the target root filesystem to be used for merging packages or ebuilds . All RDEPEND and PDEPEND will be installed into ROOT while all DEPEND will be still be installed into / . Typically, you should set this setting in the environment rather than in /etc/make.conf itself. It is commonly used for creating new build images. Make sure you use an absolute path.
Defaults to / .

RPMDIR = [path] ¶

Defines the location where created RPM packages will be stored.
Defaults to $/rpm .

SYNC = [RSYNC] ¶

Insert your preferred rsync mirror here. This rsync server is used to sync the local portage tree when ’emerge —sync’ is run.
Defaults to rsync://rsync.gentoo.org/gentoo-portage

USE = [space delimited list of USE items] ¶

This variable contains options that control the build behavior of several packages. More information in ebuild(5). Possible USE values can be found in /usr/portage/profiles/use.desc .

USE_EXPAND = [space delimited list of variable names] ¶

Any variable listed here will be used to augment USE by inserting a new flag for every value in that variable, so USE_EXPAND = «FOO» and FOO = «bar bla» results in USE = «foo_bar foo_bla» .

USE_EXPAND_HIDDEN = [space delimited list of variable names] ¶

Names of USE_EXPAND variables that should not be shown in the verbose merge list output of the emerge(1) command.

USE_ORDER = «env:pkg:conf:defaults:pkginternal:env.d» ¶

Determines the precedence of layers in the incremental stacking of the USE variable. Precedence decreases from left to right such that env overrides pkg , pkg overrides conf , and so forth.

*** WARNING *** WARNING » >¶

Do not modify this value unless you are a developer and you know what you are doing. If you change this and something breaks, we will not help you fix it.

USE from the current environment variables ( USE and those listed in USE_EXPAND )

Per-package USE from /etc/portage/package.use (see portage(5))

USE from make.conf

defaults ¶

USE from make.defaults and package.use in the profile (see portage(5))

pkginternal ¶

USE from ebuild(5) IUSE defaults

USE from the environment variables defined by files in /etc/env.d/

REPORTING BUGS¶

AUTHORS¶

Daniel Robbins
Nicholas Jones
Mike Frysinger
Saleem Abdulrasool

FILES¶

/etc/make.conf and /etc/portage/make.conf ¶

Contains variables for the build-process and overwrites those in make.defaults .

/usr/share/portage/config/make.globals ¶

Contains the default variables for the build-process, you should edit /etc/make.conf instead.

/etc/portage/color.map ¶

Contains variables customizing colors.

/usr/portage/profiles/use.desc ¶

Contains a list of all global USE flags.

/usr/portage/profiles/use.local.desc ¶

Contains a list of all local USE variables.

Источник