pacman (gerenciador de pacotes do Arch) (makepkg.conf)

makepkg -sri

Categoria: Miscelânea

Software: pacman (gerenciador de pacotes do Arch)

[ Hits: 3.153 ]

Por: niquelnausea


Faça um backup e substitua o arquivo /etc/makepkg.conf.

Ele é o arquivo responsável pelas configurações que serão utilizadas para compilações de pacotes no Arch atraves dos PKGBUILD oficiais ou do AUR, que posteriormente serão instalados através do pacman.

Nessa configuração, o compilador irá usar as flags específicas do seu processador, acelerando a compilação e tornando o binário mais rápido para seu sistema.

Nesta configuração, está desabilitada a compressão do pacote compilado (a compressão é interessante apenas se você deseja disponibilizar o pacote via rede).

As opções na parte inferior "export CC=clang" e "export CXX=clang++" podem ser habilitadas caso queira compilar utilizando o LLVM em vez do GCC.


#
# /etc/makepkg.conf
#

#########################################################################
# SOURCE ACQUISITION
#########################################################################
#
#-- The download utilities that makepkg should use to acquire sources
#  Format: 'protocol::agent'
DLAGENTS=('ftp::/usr/bin/curl -fC - --ftp-pasv --retry 3 --retry-delay 3 -o %o %u'
          'http::/usr/bin/curl -fLC - --retry 3 --retry-delay 3 -o %o %u'
          'https::/usr/bin/curl -fLC - --retry 3 --retry-delay 3 -o %o %u'
          'rsync::/usr/bin/rsync --no-motd -z %u %o'
          'scp::/usr/bin/scp -C %u %o')

# Other common tools:
# /usr/bin/snarf
# /usr/bin/lftpget -c
# /usr/bin/wget

#-- The package required by makepkg to download VCS sources
#  Format: 'protocol::package'
VCSCLIENTS=('bzr::bzr'
            'git::git'
            'hg::mercurial'
            'svn::subversion')

#########################################################################
# ARCHITECTURE, COMPILE FLAGS
#########################################################################
#
CARCH="x86_64"
CHOST="x86_64-archlinux-gnu"

#-- Compiler and Linker Flags
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=native -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4"
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro"
#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j5"
#-- Debugging flags
DEBUG_CFLAGS="-g -fvar-tracking-assignments"
DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"

#########################################################################
# BUILD ENVIRONMENT
#########################################################################
#
# Defaults: BUILDENV=(!distcc color ccache check !sign)
#  A negated environment option will do the opposite of the comments below.
#
#-- distcc:   Use the Distributed C/C++/ObjC compiler
#-- color:    Colorize output messages
#-- ccache:   Use ccache to cache compilation
#-- check:    Run the check() function if present in the PKGBUILD
#-- sign:     Generate PGP signature file
#
BUILDENV=(!distcc color !ccache check !sign)
#
#-- If using DistCC, your MAKEFLAGS will also need modification. In addition,
#-- specify a space-delimited list of hosts running in the DistCC cluster.
#DISTCC_HOSTS=""
#
#-- Specify a directory for package building.
#BUILDDIR=/tmp/makepkg

#########################################################################
# GLOBAL PACKAGE OPTIONS
#   These are default values for the options=() settings
#########################################################################
#
# Default: OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !upx !debug)
#  A negated option will do the opposite of the comments below.
#
#-- strip:      Strip symbols from binaries/libraries
#-- docs:       Save doc directories specified by DOC_DIRS
#-- libtool:    Leave libtool (.la) files in packages
#-- staticlibs: Leave static library (.a) files in packages
#-- emptydirs:  Leave empty directories in packages
#-- zipman:     Compress manual (man and info) pages in MAN_DIRS with gzip
#-- purge:      Remove files specified by PURGE_TARGETS
#-- upx:        Compress binary executable files using UPX
#-- debug:      Add debugging flags as specified in DEBUG_* variables
#
OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !upx !debug)

#-- File integrity checks to use. Valid: md5, sha1, sha256, sha384, sha512
INTEGRITY_CHECK=(md5)
#-- Options to be used when stripping binaries. See `man strip' for details.
STRIP_BINARIES="--strip-all"
#-- Options to be used when stripping shared libraries. See `man strip' for details.
STRIP_SHARED="--strip-unneeded"
#-- Options to be used when stripping static libraries. See `man strip' for details.
STRIP_STATIC="--strip-debug"
#-- Manual (man and info) directories to compress (if zipman is specified)
MAN_DIRS=({usr{,/local}{,/share},opt/*}/{man,info})
#-- Doc directories to remove (if !docs is specified)
DOC_DIRS=(usr/{,local/}{,share/}{doc,gtk-doc} opt/*/{doc,gtk-doc})
#-- Files to be removed from all packages (if purge is specified)
PURGE_TARGETS=(usr/{,share}/info/dir .packlist *.pod)

#########################################################################
# PACKAGE OUTPUT
#########################################################################
#
# Default: put built package and cached source in build directory
#
#-- Destination: specify a fixed directory where all packages will be placed
#PKGDEST=/home/packages
#-- Source cache: specify a fixed directory where source files will be cached
#SRCDEST=/home/sources
#-- Source packages: specify a fixed directory where all src packages will be placed
#SRCPKGDEST=/home/srcpackages
#-- Log files: specify a fixed directory where all log files will be placed
#LOGDEST=/home/makepkglogs
#-- Packager: name/email of the person or organization building packages
#PACKAGER="John Doe <john@doe.com>"
#-- Specify a key to use for package signing
#GPGKEY=""

#########################################################################
# COMPRESSION DEFAULTS
#########################################################################
#
COMPRESSGZ=(gzip -c -f -n)
COMPRESSBZ2=(bzip2 -c -f)
COMPRESSXZ=(xz -c -z -T 0)
COMPRESSLRZ=(lrzip -q)
COMPRESSLZO=(lzop -q)
COMPRESSZ=(compress -c -f)

#########################################################################
# EXTENSION DEFAULTS
#########################################################################
#
# WARNING: Do NOT modify these variables unless you know what you are
#          doing.
#
#PKGEXT='.pkg.tar.xz'
PKGEXT='.pkg.tar'
SRCEXT='.src.tar.gz'

# vim: set ft=sh ts=2 sw=2 et:

#export CC=clang
#export CXX=clang++
  


Comentários
[1] Comentário enviado por eldermf em 22/07/2015 - 09:56h

Bom dia, li este artigo e fiquei curioso para saber mais sobre estas "FLAGS" que também são comuns no GENTOO. Na linha postada:
"#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j5"" ---> Vem a DÚVIDA: Meu notebook é um Dell iCore 3, então a sintaxe correta para o meu caso seria;

MAKEFLAGS="-j3" ???

[2] Comentário enviado por niquelnausea em 22/07/2015 - 21:00h


[1] Comentário enviado por eldermf em 22/07/2015 - 09:56h

Bom dia, li este artigo e fiquei curioso para saber mais sobre estas "FLAGS" que também são comuns no GENTOO. Na linha postada:
"#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j5"" ---&gt; Vem a DÚVIDA: Meu notebook é um Dell iCore 3, então a sintaxe correta para o meu caso seria;

MAKEFLAGS="-j3" ???


use o numero de núcleos de seu processador + 1.

uma das maneiras de se descobrir:

grep "model name" /proc/cpuinfo | wc -l

[3] Comentário enviado por eldermf em 23/07/2015 - 09:34h

Ok, obrigado por me responder.
Irei testar mais tarde.

[4] Comentário enviado por DanielDutra em 20/08/2016 - 22:28h


[2] Comentário enviado por niquelnausea em 22/07/2015 - 21:00h

use o numero de núcleos de seu processador + 1.

uma das maneiras de se descobrir:

grep "model name" /proc/cpuinfo | wc -l


Companheiro digitei o comando grep "model name" /proc/cpuinfo | wc -l ele mostra a quantidade de nucleos que o meu processador possui?


[5] Comentário enviado por niquelnausea em 25/08/2016 - 22:56h


Companheiro digitei o comando grep "model name" /proc/cpuinfo | wc -l ele mostra a quantidade de nucleos que o meu processador possui?


sim, pode usar também o comando nproc.



Contribuir com comentário

  



Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts