Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
post your make.conf
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... , 17, 18, 19  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo Chat
View previous topic :: View next topic  
Author Message
freke
Guru
Guru


Joined: 23 Jan 2003
Posts: 591
Location: Somewhere in Denmark

PostPosted: Sun Jan 12, 2020 10:25 pm    Post subject: Reply with quote

PCEngines APU2D4 board (x4)
Code:
CFLAGS="-fgraphite-identity -floop-interchange -ftree-loop-distribution -floop-strip-mine -floop-block"
CFLAGS="${CFLAGS} -flto=4 -fuse-linker-plugin -fno-fat-lto-objects"
CFLAGS="${CFLAGS} -O2 -pipe -fomit-frame-pointer"
CFLAGS="${CFLAGS} -march=btver2 -mmmx -mno-3dnow -msse -msse2 -msse3 -mssse3 -msse4a -mcx16 -msahf -mmovbe -maes -mno-sha -mpclmul -mpopcnt -mabm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mbmi -mno-sgx -mno-bmi2 -mno-pconfig -mno-wbnoinvd -mno-tbm -mavx -mno-avx2 -msse4.2 -msse4.1 -mlzcnt -mno-rtm -mno-hle -mno-rdrnd -mf16c -mno-fsgsbase -mno-rdseed -mprfchw -mno-adx -mfxsr -mxsave -mxsaveopt -mno-avx512f -mno-avx512er -mno-avx512cd -mno-avx512pf -mno-prefetchwt1 -mno-clflushopt -mno-xsavec -mno-xsaves -mno-avx512dq -mno-avx512bw -mno-avx512vl -mno-avx512ifma -mno-avx512vbmi -mno-avx5124fmaps -mno-avx5124vnniw -mno-clwb -mno-mwaitx -mno-clzero -mno-pku -mno-rdpid -mno-gfni -mno-shstk -mno-avx512vbmi2 -mno-avx512vnni -mno-vaes -mno-vpclmulqdq -mno-avx512bitalg -mno-movdiri -mno-movdir64b -mno-waitpkg -mno-cldemote -mno-ptwrite --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=2048 -mtune=btver2"
CFLAGS="${CFLAGS} -ftree-vectorize"
CXXFLAGS="${CFLAGS}"
CXXFLAGS="${CFLAGS} -flifetime-dse=1"
LDFLAGS="-Wl,-O1 -Wl,--as-needed ${CXXFLAGS}"
FCFLAGS="${CFLAGS}"
FFLAGS="${CFLAGS}"
MAKEOPTS="-j33 -l6"
CHOST="x86_64-pc-linux-gnu"
CPU_FLAGS_X86="aes avx f16c mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3"

AR="gcc-ar"
NM="gcc-nm"
RANLIB="gcc-ranlib"

PORTDIR="/opt/portage"
DISTDIR="/opt/distfiles"
PKGDIR="/opt/bindir"
INSTALL_MASK="/etc/systemd /lib/systemd /usr/lib/systemd"
FEATURES="buildpkg distcc"

USE="-anacron berkdb caps gd -gdbm geoip2 gnutls graphite idn -introspection leaps-timezone lto pgo pps syslog udev usb"

PORTAGE_GPG_DIR="/var/lib/gentoo/gkeys/keyrings/gentoo/release"

ALSA_CARDS=""
ALSA_PCM_PLUGINS=""
CALLIGRA_FEATURES=""
CAMERAS=""
COLLECTD_PLUGINS=""
GPSD_PROTOCOLS="garmin"
LCD_DEVICES=""
LIBREOFFICE_EXTENSIONS=""
OFFICE_IMPLEMENTATION=""
VIDEO_CARDS=""
XTABLES_ADDONS=""

PORTAGE_ELOG_SYSTEM="save mail"
PORTAGE_ELOG_CLASSES="warn error log qa"
PORTAGE_ELOG_MAILURI="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
PORTAGE_ELOG_MAILFROM="xxxxxxxxxxxxxxxxx"

GENTOO_MIRRORS="http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ http://trumpetti.atm.tut.fi/gentoo/"

# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C


Using distcc - otherwise it'd been march=native...
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 46272
Location: 56N 3W

PostPosted: Sun Jan 12, 2020 10:52 pm    Post subject: Reply with quote

freke,

You can drop all the -mno-* options.
Try
Code:
gcc -### -E - -march=native 2>&1 | sed -r '/cc1/!d;s/(")|(^.* - )|( -mno-[^\ ]+)//g'

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2835
Location: Canada

PostPosted: Mon Jan 13, 2020 12:36 am    Post subject: Reply with quote

Hm, why do people have CPU_FLAGS ? Never thought of this before.
Back to top
View user's profile Send private message
superjaded
l33t
l33t


Joined: 05 Jul 2002
Posts: 791

PostPosted: Mon Jan 13, 2020 1:17 am    Post subject: Reply with quote

dmpogo wrote:
Hm, why do people have CPU_FLAGS ? Never thought of this before.


Are you talking about CPU_FLAGS_X86? If so, check out this article. Basically it determines what extension flags to compile packages with that support it.
Back to top
View user's profile Send private message
kajzer
l33t
l33t


Joined: 27 Nov 2014
Posts: 811

PostPosted: Mon Jan 13, 2020 10:51 am    Post subject: Reply with quote

Seems like everything is moving from make.conf to package.use
Back to top
View user's profile Send private message
freke
Guru
Guru


Joined: 23 Jan 2003
Posts: 591
Location: Somewhere in Denmark

PostPosted: Mon Jan 13, 2020 3:03 pm    Post subject: Reply with quote

NeddySeagoon wrote:
freke,

You can drop all the -mno-* options.
Try
Code:
gcc -### -E - -march=native 2>&1 | sed -r '/cc1/!d;s/(")|(^.* - )|( -mno-[^\ ]+)//g'


Thanks - will give it a spin, I used
Code:
gcc -### -E - -march=native 2>&1 | sed -r '/cc1/!d;s/(")|(^.* - )//g'
found here https://github.com/distcc/distcc/issues/331
Back to top
View user's profile Send private message
Ionen
Veteran
Veteran


Joined: 06 Dec 2018
Posts: 1247

PostPosted: Mon Jan 13, 2020 4:00 pm    Post subject: Reply with quote

kajzer wrote:
Seems like everything is moving from make.conf to package.use
It make more sense if anything, make.conf is mostly for portage itself configuration, not USE flags. And USE_EXPAND-type variables are a simplified shortcut expanded to USE flags.

Not to mention most USE_EXPAND variables shouldn't even be set at all in the first place, gentoo will just update their defaults when judged necessary. They are only there for if you have a reason to deviate from the defaults, most users in fact do not and just have a old value left outdated in their make.conf causing problems (setting yourself does make sense for hardware-specific things like VIDEO_CARDS though)

Can review which variables are in that subset by using "emerge --info | grep ^USE_EXPAND=".

Edit: For anyone else reading this, yet another reminder to either set your PYTHON_* variables as documented or not at all, in case of python it can actually cause problems if still in make.conf. For others, I don't think it matters (wiki says either make.conf or package.use, for now anyway), but personally I'd rather keep USE flags where they belong, even if not expanded yet ;) Also relatively easier to control there (add to default, remove specific target from defaults if it exists, etc.. without having to set the whole variable in stone even if the defaults change)
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2835
Location: Canada

PostPosted: Mon Jan 13, 2020 10:27 pm    Post subject: Reply with quote

superjaded wrote:
dmpogo wrote:
Hm, why do people have CPU_FLAGS ? Never thought of this before.


Are you talking about CPU_FLAGS_X86? If so, check out this article. Basically it determines what extension flags to compile packages with that support it.



How to find what packages use this variable ? I always thought compiler checks what optimization/instructions my CPU supports :)
Back to top
View user's profile Send private message
Ionen
Veteran
Veteran


Joined: 06 Dec 2018
Posts: 1247

PostPosted: Mon Jan 13, 2020 10:47 pm    Post subject: Reply with quote

dmpogo wrote:
How to find what packages use this variable ? I always thought compiler checks what optimization/instructions my CPU supports :)
Normally yes, but not all code is handled by the compiler. For example some packages will use ASM directly for specific optimizations, and rather than try to guess themselves will offer a --enable-someCPUinstruction flag (that most binary distributions would disable).

The actual expanded USE flag will look like "cpu_flags_x86_avx2" (avx2 being the instruction) then you can check like any other USE flags. Most commonly you'll see media-encoders/ffmpeg/math/cryptography/emulators where performance matter use those.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 46272
Location: 56N 3W

PostPosted: Mon Jan 13, 2020 10:53 pm    Post subject: Reply with quote

dmpogo,

CPU_FLAGS_X86 is to activate hand optimised assembler code in some programs.
That not the same as -march=-native

Assembler is passed through gcc unchanged, so if there are mmx or 3dnow options, CPU_FLAGS_X86 selects the assembler code you tell it do.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2835
Location: Canada

PostPosted: Mon Jan 13, 2020 11:15 pm    Post subject: Reply with quote

NeddySeagoon wrote:
dmpogo,

CPU_FLAGS_X86 is to activate hand optimised assembler code in some programs.
That not the same as -march=-native

Assembler is passed through gcc unchanged, so if there are mmx or 3dnow options, CPU_FLAGS_X86 selects the assembler code you tell it do.



Thanks, but does this variable expands into USE flags ? I did not find any package from installed on my machines that does not already use all flags that cpuid2flags sets for CPU_FLAGS_X86.
Back to top
View user's profile Send private message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 3510

PostPosted: Tue Jan 14, 2020 7:15 am    Post subject: Reply with quote

dmpogo wrote:
Thanks, but does this variable expands into USE flags ? ...

See https://packages.gentoo.org/useflags/search?q=cpu_flags_x86
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 46272
Location: 56N 3W

PostPosted: Tue Jan 14, 2020 9:29 am    Post subject: Reply with quote

dmpogo,

It does. It used to be ordinary USE flags before it was moved to a USE_EXPAND.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2835
Location: Canada

PostPosted: Tue Jan 14, 2020 5:16 pm    Post subject: Reply with quote

NeddySeagoon wrote:
dmpogo,

It does. It used to be ordinary USE flags before it was moved to a USE_EXPAND.



Yes indeed, found them, it was my misunderstanding in the beginning. However, what I find is that all the packages that have those USE_EXPOAND type flags,
happen to be compiled (*) with appropiate for CPU combination (different on my different machines) enabled, despite the fact that I
forgot to set CPU_FLAGS_X86 in make.conf. Except one machine that had some old cruft 'mmx sse' etc in USE statement in make.conf.
For this machine flags that were not explicitly in USE were skipped. So is there some autodetection logic present ?

(*) if I interpret 'I' column in equery uses PKG output correctly.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 46272
Location: 56N 3W

PostPosted: Tue Jan 14, 2020 5:48 pm    Post subject: Reply with quote

dmpogo,

For every CPU_FLAGS_X86 flag, gcc has a similarly named CFLAG flag. Sometimes identical. The two do totally different things.

The CFLAG being on gives gcc permission (there is no compulsion) to use the flags instruction set extension if it wants.
This only affects high level languages in GCC.

The CPU_FLAGS_X86 being on compels the build system to select hand optimised code that requires the instruction set extension.
This hand optimised code is usually assembler.

One affects what gcc may do. The other affects the build system.

If you turn on a CFLAG that your CPU does not support, the resulting binary may not run. It depends on what gcc did.
If you turn on a CPU_FLAGS_X86 your system does not support, the code will break when the optimised code path is executed.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2835
Location: Canada

PostPosted: Tue Jan 14, 2020 11:27 pm    Post subject: Reply with quote

NeddySeagoon wrote:
dmpogo,

For every CPU_FLAGS_X86 flag, gcc has a similarly named CFLAG flag. Sometimes identical. The two do totally different things.

The CFLAG being on gives gcc permission (there is no compulsion) to use the flags instruction set extension if it wants.
This only affects high level languages in GCC.

The CPU_FLAGS_X86 being on compels the build system to select hand optimised code that requires the instruction set extension.
This hand optimised code is usually assembler.

One affects what gcc may do. The other affects the build system.

If you turn on a CFLAG that your CPU does not support, the resulting binary may not run. It depends on what gcc did.
If you turn on a CPU_FLAGS_X86 your system does not support, the code will break when the optimised code path is executed.


Sure, that was not the questions. The question is that all cpu_flag_x86_??? USE options happened to be enabled exactly correctly for my CPU's without me havng
CPU_FLAG_X86 variable defined in make.conf. So how did this happen ?
Back to top
View user's profile Send private message
keremCozin
n00b
n00b


Joined: 18 Sep 2017
Posts: 4

PostPosted: Mon Jan 20, 2020 12:42 am    Post subject: Reply with quote

Code:
### GENTOO STABLE BUILD ###
        ACCEPT_KEYWORDS="amd64"
        ACCEPT_LICENSE="*"

### COMPILER ATTRIBUTES ###
        CHOST="x86_64-pc-linux-gnu"
        COMMON_FLAGS="-march=native -O3 -pipe"
        CFLAGS="${COMMON_FLAGS}"
        CXXFLAGS="${COMMON_FLAGS}"
        FCFLAGS="${COMMON_FLAGS}"
        FFLAGS="${COMMON_FLAGS}"
        CPU_FLAGS_X86="aes avx f16c fma3 fma4 mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 xop"
        MAKEOPTS="-j4"
#       NINJAFLAGS="-j1" Fallback

### PORTAGE DIRECTORIES ###
        PORTDIR="/var/db/repos/gentoo"
        DISTDIR="/var/cache/distfiles"
        PKGDIR="/var/cache/binpkgs"

### PORTAGE OPTIONS ###
        EMERGE_DEFAULT_OPTS="--ask --verbose"
        FEATURES="${FEATURES} splitdebug"

### HARDWARE VARIABLES ###
        GRUB_PLATFORMS="efi-64"
        INPUT_DEVICES="libinput"
        VIDEO_CARDS="nvidia"
        ALSA_CARDS="hda-intel"

### GLOBAL USE FLAGS ###
        USE="efi clang lto pgo gtk3 ffmpeg python xinerama pulseaudio nsplugin pentoo opencl -wayland -handbook -cdrom"
        CALLIGRA_FEATURES="karbon sheets words stage"

### Overlays
        source /var/lib/layman/make.conf


Gentoo is amazing! Please don't flame at me for that -O3 CFLAG :roll: :lol:
Back to top
View user's profile Send private message
Ionen
Veteran
Veteran


Joined: 06 Dec 2018
Posts: 1247

PostPosted: Mon Jan 20, 2020 3:12 am    Post subject: Reply with quote

dmpogo wrote:
The question is that all cpu_flag_x86_??? USE options happened to be enabled exactly correctly for my CPU's without me having CPU_FLAG_X86 variable defined in make.conf. So how did this happen ?
While "correct" it was probably missing flags, it seem to set some "minimal" defaults for the profile (as in, what everyone should have). Like if I have mine unset, I get in emerge --info "mmx mmxext sse sse2" but my full list is "aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3"

keremCozin wrote:
Please don't flame at me for that -O3 CFLAG :roll: :lol:
Usually it's fine, and the known issues get filtered by ebuilds since gentoo knows that a lot of people throw -O3 in there anyway :) That aside, if you ever get strange run time behavior, do remember to try without.
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 975

PostPosted: Mon Jan 20, 2020 5:23 am    Post subject: Reply with quote

Code:
# These settings were set by the catalyst build script that automatically built this stage. Please consult /usr/share/portage/config/make.conf.example for a more  detailed example.
COMMON_FLAGS="-march=native -mtune=native -O2 -pipe -flto=7 -fomit-frame-pointer -ftree-vectorize -fuse-linker-plugin -fno-plt -fno-stack-protector -s"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--sort-common -Wl,--strip-debug -Wl,--discard-all -flto=7 -fuse-linker-plugin -s"
MAKEOPTS="-j7"
PORTAGE_NICENESS="19"

# Portage directories
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/tmp"

# This sets the language of build output to English. Please keep this setting intact when reporting bugs.
LC_MESSAGES=C

# Accepts
ACCEPT_KEYWORDS="~amd64"
ACCEPT_LICENSE="*"

# Features
FEATURES="-nostrip parallel-fetch parallel-install userfetch unmerge-orphans"
# USE Flags
USE="X -accessibility alsa bash-completion -berkdb -bluetooth bzip2 cairo -consolekit -coreaudio -cracklib -crypt cups custom-cflags dbus -debug -doc elogind -encode ffmpeg flac fontconfig -fortran gif gmp -gnome -gstreamer -gtk -gtk-doc -handbook icu introspection -ipv6 jpeg kde lcms -libnotify lzma lzo -mad mmap -mp3 -mp4 -mpeg mtp nls -odbc ogg opengl openmp orc -oss pch -pcmcia -perl png pulseaudio -python -qdbm -qt5 -ruby -samba -sdl -selinux -semantic-desktop -smartcard -speex ssl -startup-notification -static -static-libs symlink svg -systemd -tcpd tiff threads truetype udev unicode vaapi -vanilla -vdpau vorbis wavpack -wayland webp -vala xcb xft xmpp -yahoo zip zlib -zsh-completion zstd"
CPU_FLAGS_X86="aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3"
PYTHON_TARGETS="python3_8"
PYTHON_SINGLE_TARGET="python3_8"
RUBY_TARGETS="ruby27"
LLVM_TARGETS=""
FFTOOLS=""
INPUT_DEVICES="libinput"
VIDEO_CARDS="intel i965"
L10N="en en_US en-US ru ru_RU ru-RU"
LINGUAS="en en_US en-US ru ru_RU ru-RU"
#
INSTALL_MASK="/lib/systemd /usr/lib/systemd /usr/share/zsh"
#
CCACHE_DIR="/var/tmp/ccache"

It's strange but with '-Wl,--strip-debug' binaries are smaller that with '-Wl,--strip-all'.

And also setting for packages build with LLVM/Clang:
Code:
~ $ cat /etc/portage/env/clang_compiler
CC="clang"
CXX="clang++"
COMMON_FLAGS="-march=native -mtune=native -O3 -pipe -flto=thin -fomit-frame-pointer -fno-plt -fno-stack-protector -fno-unwind-tables"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS} -stdlib=libc++"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--strip-all -Wl,--discard-all -flto=thin -Wl,--thinlto-jobs=7 -fuse-ld=lld -rtlib=compiler-rt -unwindlib=libunwind -s"

AR="llvm-ar"
OBJCOPY="llvm-objcopy"
OBJDUMP="llvm-objdump"
NM="llvm-nm"
RANLIB="llvm-ranlib"
READELF="llvm-readelf"
STRIP="llvm-strip"
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2835
Location: Canada

PostPosted: Mon Jan 20, 2020 7:01 am    Post subject: Reply with quote

Ionen wrote:
dmpogo wrote:
The question is that all cpu_flag_x86_??? USE options happened to be enabled exactly correctly for my CPU's without me having CPU_FLAG_X86 variable defined in make.conf. So how did this happen ?
While "correct" it was probably missing flags, it seem to set some "minimal" defaults for the profile (as in, what everyone should have). Like if I have mine unset, I get in emerge --info "mmx mmxext sse sse2" but my full list is "aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3"


Funny part in my case, that no flags were missing, from essentially as long list as yours (KabyLake i7). Well, almost. Yesterday I did find one package that was missing f16c
Back to top
View user's profile Send private message
alexander-n8hgeg5e
n00b
n00b


Joined: 02 Nov 2019
Posts: 32

PostPosted: Sun Jan 26, 2020 4:14 am    Post subject: Reply with quote

This is my /etc/portage/profile/make.defaults
Without this it would be incomplete
Probably many things can be done better.
for example, i set EROOT and i don't know whether and why i need this.
But if i would remove such a line probably something breaks.
This is mainly i think to get the same config working with eprefix.

Code:

## software
#ACCEPT_LICENSE="-* @FREE"

EROOT="/"

# files and dir here allowed
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/fish/conf.d"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/ssh/ssh_config"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/vim"

CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/portage/package.use"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/portage/package.accept_keywords"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/portage/package.mask"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/portage/package.unmask"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/portage/env"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/portage/package.env"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/portage/package.license"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/git_hooks"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/init.d"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/resolvconf.conf"

#CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/locale.conf"
CONFIG_PROTECT_MASK="${CONFIG_PROTECT_MASK} ${EROOT}etc/locale.gen"

FEATURES="${FEATURES} candy"                                                      # look
FEATURES="${FEATURES} python-trace unknown-features-warn"                         # debugging
FEATURES="${FEATURES} preserve-libs protect-owned buildsyspkg"                    # function
FEATURES="${FEATURES} sandbox usersandbox userpriv"                               # security
FEATURES="${FEATURES} strict suidctl"                                             # security
FEATURES="${FEATURES} parallel-install parallel-fetch python-trace cgroup"        # speed

USE="${USE} tcpd pulseaudio opengl X bluetooth truetype jpeg tiff ogg -nls -javascript"
PYTHON_TARGETS="python2_7 python3_6 python3_7"
RUBY_TARGETS="ruby24"

USE_EXPAND="${USE_EXPAND} TFTPD_FCAP_USERS"
USE_EXPAND_IMPLICIT="${USE_EXPAND_IMPLICIT} TFTPD_FCAP_USERS"
USE_EXPAND_VALUES_TFTPD_FCAP_USERS="dusteater skyscraper"

#L10N="en"
#LINGUAS="en"

## some vars
CODEDIR="${EROOT}code"
MYGITHUB_URIBASE="https://github.com/alexander-n8hgeg5e/"

## portage config
GENTOO_MIRRORS="${GENTOO_MIRRORS} \
http://mirrors.soeasyto.com/distfiles.gentoo.org/ \
http://mirror.eu.oneandone.net/linux/distributions/gentoo/gentoo/ \
ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo \
ftp://mirror.netcologne.de/gentoo/ \
http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ \
http://gentoo.inode.at/ \
http://gd.tuwien.ac.at/opsys/linux/gentoo/ \
http://mirror.netcologne.de/gentoo/ \
http://ftp-stud.hs-esslingen.de/pub/Mirrors/gentoo/ \
ftp://mirror.leaseweb.com/gentoo/ \
http://ftp.heanet.ie/pub/gentoo/ \
http://ftp.halifax.rwth-aachen.de/gentoo/ \
http://distfiles.gentoo.org \
http://www.ibiblio.org/pub/Linux/distributions/gentoo"

PORTDIR="${EROOT}usr/portage"
PORTAGE_LOGDIR="${EROOT}var/log/portage"
PORTAGE_GPG_DIR="${EROOT}etc/portage/gpg"
PKGDIR="${EROOT}usr/portage/packages"
CCACHE_DIR="${EROOT}var/tmp/ccache"
SYNC=""
PORTAGE_ELOG_CLASSES="warn error log"
PORTAGE_ELOG_SYSTEM="echo save:error"
PORTAGE_WORKDIR_MODE="0750"

EMERGE_DEFAULT_OPTS="\
                     --keep-going y                          \
                     --quiet-build                           \
                     --autounmask y                          \
                     --autounmask-continue y                 \
                     --autounmask-keep-keywords y            \
                     --autounmask-keep-masks y               \
                     --autounmask-write y                    \
                     --autounmask-backtrack y                \
                     --backtrack=30"                         
#                     --complete-graph                        \
#                     --use-ebuild-visibility"
#                     --newrepo                               \
#                     --rebuild-if-new-slot y                 \
#                     --rebuild-if-unbuilt y                  \
#                     --rebuild-if-new-rev y                  \
#                     --rebuild-if-new-ver y                  \

make.conf
Code:

### machine: dusteater
EROOT="/"
#source /usr/share/mydefaults/make.default

## hardware

# core
CHOST="x86_64-pc-linux-gnu"
CPU_FLAGS_X86="3dnow 3dnowext mmx mmxext popcnt sse sse2 sse3 sse4a"
CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer"
CXXFLAGS="${CFLAGS}"

# other
INPUT_DEVICES="evdev"
GRUB_PLATFORMS="pc"
VIDEO_CARDS="nouveau"

## software
## todo remove following line
ACCEPT_LICENSE="* -@EULA"
USE="tcpd pulseaudio opengl X bluetooth truetype jpeg tiff ogg -bindist \
     -multilib python sound mbox jpeg2k pdf png postscript svg \
     -qt3support qml opus qt5 eme-free system-libvpx system-libevent \
     system- system-icu system-harfbuzz system-cairo tk sqlite \
     -gnome-keyring metric apng icu minizip theora xetex text gui \
     widgets x264 aac system-ffmpeg sdl vpx xvid ffmpeg dmx neovim \
     rind nouveau vdpau vim-syntax fish-completion dmenu nfsv41 x265 \
     mng exif xpm libcaca ncurses pyopen webengine -webkit network \
     printsupport webchannel sql openssl -cups mpi mpi-threads \
     remote djvu -policykit -dbus -nls"
QEMU_SOFTMMU_TARGETS="i386 x86_64 arm"
QEMU_USER_TARGETS="i386 x86_64 arm"
RUBY_TARGETS="${RUBY_TARGETS} ruby20 ruby21 ruby22 ruby23"
PYTHON_SINGLE_TARGET="python3_7"

## speed
MAKEOPTS="-j24 -l100"
#MAKEOPTS=" -j1 -l6"
EMERGE_DEFAULT_OPTS="${EMERGE_DEFAULT_OPTS} --jobs 16 --load-average 100"
#EMERGE_DEFAULT_OPTS="${EMERGE_DEFAULT_OPTS} --jobs 1 --load-average 6"

## portage

PORTAGE_TMPDIR="/var/tmp/dusteater"
PORTAGE_LOGDIR="/tmp${PORTAGE_LOGDIR}"


# Enable ccache
FEATURES="${FEATURES} ccache"
FEATURES="${FEATURES} -xattr"
CCACHE_SIZE="50G"
CCACHE_DIR="/var/tmp/dusteater/ccache"

BINPKG_COMPRESS=""
Back to top
View user's profile Send private message
tzycce
n00b
n00b


Joined: 05 Nov 2019
Posts: 15

PostPosted: Mon Feb 17, 2020 9:24 pm    Post subject: Reply with quote

Not sure if this makes much sense but it is working so far. Using sway

Code:
i# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
COMMON_FLAGS=-"march=ivybridge -O2 -pipe"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
CHOST="x86_64-pc-linux-gnu"
CPU_FLAGS_X86="aes avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3"
VIDEO_CARDS="intel i965"
USE="acpi alsa bash-completion emacs ncurses glamor truetype ttf vim-syntax wayland xattr -gnome -kde -pulseaudio -startup-notification -systemd"
MAKEOPTS="-j4"
ACCEPT_LICENSE="*"
# NOTE: This stage was built with the bindist Use flag enabled
PORTDIR="/var/db/repos/gentoo"
DISTDIR="/var/cache/distfiles"
PKGDIR="/var/cache/binpkgs"

# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C

GENTOO_MIRRORS="ftp://mirror.mdfnet.se/gentoo https://mirror.mdfnet.se/gentoo"
Back to top
View user's profile Send private message
fturco
Veteran
Veteran


Joined: 08 Dec 2010
Posts: 1184
Location: Italy

PostPosted: Tue Feb 18, 2020 12:29 pm    Post subject: Reply with quote

tzycce wrote:
Code:
i# These settings were set by the catalyst build script that automatically

Is the "i" letter at the beginning a typo?
Back to top
View user's profile Send private message
tzycce
n00b
n00b


Joined: 05 Nov 2019
Posts: 15

PostPosted: Wed Feb 19, 2020 10:01 am    Post subject: Reply with quote

fturco wrote:
tzycce wrote:
Code:
i# These settings were set by the catalyst build script that automatically

Is the "i" letter at the beginning a typo?

Had to check that one. Yes it was.
Back to top
View user's profile Send private message
guitou
Guru
Guru


Joined: 02 Oct 2003
Posts: 475
Location: France

PostPosted: Wed Feb 19, 2020 12:06 pm    Post subject: Reply with quote

Hello.

Strangely, I could see no trailing ":wq" :p

++
Gi)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo Chat All times are GMT
Goto page Previous  1, 2, 3 ... , 17, 18, 19  Next
Page 18 of 19

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum