Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Optimizing install-time settings to use binary host
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
lars_the_bear
Guru
Guru


Joined: 05 Jun 2024
Posts: 535

PostPosted: Thu Aug 22, 2024 7:18 am    Post subject: Optimizing install-time settings to use binary host Reply with quote

Hi folks

This is a spin-off from an earlier thread. I've been trying to work out what settings I should use, at installation time, to take advantage of the gentoo binhost. My computers are not fast at compiling, and routine updates are taking 2-3 days at 100% CPU.

In the earlier thread, @sam said:

Quote:
The binhost tries to stick to defaults on the profiles it builds for as much as possible (with some overlap between different profiles to cover common needs). Everything you configure (either enabling or disabling) is an additional constraint, whether you're using the binhost or not, and making use of the power to customise. By using that power, you then have to accept e.g. building more.


And it was suggested that I should just set no USE flags at all. So I tried this. I set up a new installation and chose profile 23 'desktop/stable'. I didn't change any USE settings from their profile defaults at all.

But still everything wants to compile. Everything seems to want +pulseaudio and +wayland (at least), neither of which are set in this profile. These settings seem almost ubiquitous.

So it doesn't look to me as if keeping to the profile defaults actually gets me any more use of the binhost. I'm aware that for monster packages like firefox and LibreOffice there are specific -bin variants, and these work fine. But for things that may or may not be available as binaries, I'm mostly not getting the binaries.

What am I continuing to fail to understand here?

All I want to do is to run a minimal-ish Linux on old-ish laptops. I don't care how I get there, but nothing I've tried so far seems to be very effective.

BR, Lars
Back to top
View user's profile Send private message
pietinger
Moderator
Moderator


Joined: 17 Oct 2006
Posts: 5161
Location: Bavaria

PostPosted: Thu Aug 22, 2024 9:25 am    Post subject: Reply with quote

Please give us the output of

* emerge --info
* grep -r --exclude-dir=savedconfig --exclude-dir=repos.conf "" /etc/portage
_________________
https://wiki.gentoo.org/wiki/User:Pietinger
Back to top
View user's profile Send private message
lars_the_bear
Guru
Guru


Joined: 05 Jun 2024
Posts: 535

PostPosted: Thu Aug 22, 2024 9:45 am    Post subject: Reply with quote

pietinger wrote:
Please give us the output of

* emerge --info
* grep -r --exclude-dir=savedconfig --exclude-dir=repos.conf "" /etc/portage


Thanks. I don't know if there's a way to attach files, or a common place to put them, so please find dump below.

Code:

Portage 3.0.65 (python 3.12.3-final-0, default/linux/amd64/23.0/desktop, gcc-13, glibc-2.39-r6, 6.6.47-gentoo-dist x86_64)
=================================================================
System uname: Linux-6.6.47-gentoo-dist-x86_64-Intel-R-_Core-TM-_i7-6820HQ_CPU_@_2.70GHz-with-glibc2.39
KiB Mem:     9153316 total,   8853952 free
KiB Swap:   16777212 total,  16777212 free
Timestamp of repository gentoo: Wed, 21 Aug 2024 00:45:00 +0000
Head commit of repository gentoo: 53444480c5b9e0f5a618162d77871e8142d13320
sh bash 5.2_p26-r6
ld GNU ld (Gentoo 2.42 p3) 2.42.0
app-misc/pax-utils:        1.3.7::gentoo
app-shells/bash:           5.2_p26-r6::gentoo
dev-build/autoconf:        2.71-r7::gentoo
dev-build/automake:        1.16.5-r2::gentoo
dev-build/cmake:           3.28.5::gentoo
dev-build/libtool:         2.4.7-r4::gentoo
dev-build/make:            4.4.1-r1::gentoo
dev-build/meson:           1.5.1::gentoo
dev-lang/perl:             5.38.2-r3::gentoo
dev-lang/python:           3.12.3-r1::gentoo
dev-lang/rust-bin:         1.79.0::gentoo
sys-apps/baselayout:       2.15::gentoo
sys-apps/openrc:           0.54.2::gentoo
sys-apps/sandbox:          2.38::gentoo
sys-devel/binutils:        2.42-r1::gentoo
sys-devel/binutils-config: 5.5::gentoo
sys-devel/gcc:             13.3.1_p20240614::gentoo
sys-devel/gcc-config:      2.11::gentoo
sys-devel/llvm:            18.1.8-r1::gentoo
sys-kernel/linux-headers:  6.6-r1::gentoo (virtual/os-headers)
sys-libs/glibc:            2.39-r6::gentoo
Repositories:

gentoo
    location: /var/db/repos/gentoo
    sync-type: rsync
    sync-uri: rsync://rsync.gentoo.org/gentoo-portage
    priority: -1000
    volatile: False
    sync-rsync-extra-opts:
    sync-rsync-verify-jobs: 1
    sync-rsync-verify-max-age: 3
    sync-rsync-verify-metamanifest: yes

Binary Repositories:

gentoobinhost
    priority: 1
    sync-uri: https://distfiles.gentoo.org/releases/amd64/binpackages/23.0/x86-64

ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="@FREE @BINARY-REDISTRIBUTABLE"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=haswell -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/sandbox.d"
CXXFLAGS="-march=haswell -O2 -pipe"
DISTDIR="/var/cache/distfiles"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GDK_PIXBUF_MODULE_FILE GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR XDG_STATE_HOME"
FCFLAGS="-march=haswell -O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs binpkg-multi-instance buildpkg buildpkg-live config-protect-if-modified distlocks ebuild-locks fixlafiles getbinpkg ipc-sandbox merge-sync merge-wait multilib-strict network-sandbox news parallel-fetch pid-sandbox pkgdir-index-trusted preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-march=haswell -O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LANG="en_GB.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs"
LEX="flex"
PKGDIR="/var/cache/binpkgs"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
SHELL="/bin/bash"
USE="X a52 aac acl acpi alsa amd64 bluetooth branding bzip2 cairo cdda cdr cet crypt cups dbus dri dts dvd dvdr elogind encode exif flac gdbm gif gpm gtk gui iconv icu ipv6 jpeg kf6compat lcms libnotify libtirpc mad mng mp3 mp4 mpeg multilib ncurses nls ogg opengl openmp pam pango pcre pdf png policykit ppds qt5 readline sdl seccomp sound spell ssl startup-notification svg test-rust tiff truetype udev udisks unicode upower usb vorbis vulkan wxwidgets x264 xattr xcb xft xml xv xvid zlib" ABI_X86="64" ADA_TARGET="gcc_12" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_anon authn_dbm authn_file authz_dbm authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir env expires ext_filter file_cache filter headers include info log_config logio mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2 aes avx avx2 pclmul popcnt rdrand sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 ntrip navcom oceanserver oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 tsip tripmate tnt ublox" GUILE_SINGLE_TARGET="3-0" GUILE_TARGETS="3-0" INPUT_DEVICES="libinput" KERNEL="linux" LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php8-2" POSTGRES_TARGETS="postgres15" PYTHON_SINGLE_TARGET="python3_12" PYTHON_TARGETS="python3_12" RUBY_TARGETS="ruby31 ruby32" VIDEO_CARDS="vmware" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipp2p iface geoip fuzzy condition tarpit sysrq proto logmark ipmark dhcpmac delude chaos account"
Unset:  ADDR2LINE, AR, ARFLAGS, AS, ASFLAGS, CC, CCLD, CONFIG_SHELL, CPP, CPPFLAGS, CTARGET, CXX, CXXFILT, ELFEDIT, EMERGE_DEFAULT_OPTS, EXTRA_ECONF, F77FLAGS, FC, GCOV, GPROF, INSTALL_MASK, LC_ALL, LD, LFLAGS, LIBTOOL, LINGUAS, MAKE, MAKEFLAGS, MAKEOPTS, NM, OBJCOPY, OBJDUMP, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PYTHONPATH, RANLIB, READELF, RUSTFLAGS, SIZE, STRINGS, STRIP, YACC, YFLAGS

===

/etc/portage/package.use/00cpu-flags:*/* CPU_FLAGS_X86: aes avx avx2 mmx mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3
/etc/portage/package.use/installkernel:sys-kernel/installkernel dracut
/etc/portage/package.use/installkernel:sys-kernel/installkernel grub
/etc/portage/package.use/installkernel:
/etc/portage/package.use/installkernel:
/etc/portage/package.use/xfce4:>=media-libs/mesa-24.1.3 xa
/etc/portage/package.use/xfce4:
/etc/portage/binrepos.conf/gentoobinhost.conf:# These settings were set by the catalyst build script that automatically
/etc/portage/binrepos.conf/gentoobinhost.conf:# built this stage.
/etc/portage/binrepos.conf/gentoobinhost.conf:# Please consider using a local mirror.
/etc/portage/binrepos.conf/gentoobinhost.conf:
/etc/portage/binrepos.conf/gentoobinhost.conf:[gentoobinhost]
/etc/portage/binrepos.conf/gentoobinhost.conf:priority = 1
/etc/portage/binrepos.conf/gentoobinhost.conf:sync-uri = https://distfiles.gentoo.org/releases/amd64/binpackages/23.0/x86-64
/etc/portage/gnupg/dirmngr.conf:honor-http-proxy
/etc/portage/gnupg/dirmngr.conf:no-use-tor
/etc/portage/gnupg/dirmngr.conf:
/etc/portage/gnupg/dirmngr.conf:resolver-timeout 180
/etc/portage/gnupg/dirmngr.conf:connect-timeout 180
/etc/portage/gnupg/gpg-agent.conf:disable-scdaemon
/etc/portage/gnupg/gpg.conf:no-greeting
/etc/portage/gnupg/gpg.conf:no-permission-warning
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key:Created: 20240821T185357
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key:Key: (protected-private-key (rsa (n #00A8B9DC0A4397BCF015029B5EB0E99A99
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: CDC4EBEC4A9E409B42DF2E7F22A591851DECD0D59C72B61BC7D474B4F5A574E32817F5
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 3B2062FD75D574B24AF61623E05821F8F085B9A9E210DD45AFF10F3C4FCA5B607C5CB3
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 8804A0702CEF1C755B27544ED6F2ADCC5308F1A44AAFAACEF13EE1040FA34B58F8C214
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: D21748BA87850F8C6F838B6C8DFFB6BB937B78E8FAD9E4F8B302D6A3E3E24BC2B1E28C
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: CEB73DA0736FB4537A2BE1618E2DCD45907027CB9D841EEAAD22B85A0EC025677B2FD2
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 9F0A670203CD0167370F9C3CB7FA23AAD332E4C9A11922FD40150F51206A0A1640F962
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 4C27D6D88A34F9FBBDD179BCE746B32E44D3B3922697CAF359A7188FD082EDD1F9A6E1
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 3497144FC71692D5F929C6627441527069E2695A29D4D1526336E993D80A015EB6C3BA
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 260A6CEF0A8966CE1B0927BECB65CA4E7FBE9EBC12EB9397D6F70FE5E991A8EDCA50DB
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: DFDED9C9A814086DFF5A6B6BB20D7416053E12C143E09B8A211CA2A835C1E26C21F0F4
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 91DA6014644CA6DF1B3725B847CF71EF18DD#)(e #010001#)(protected
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key:  openpgp-s2k3-ocb-aes ((sha1 #6C9CCC992C178EBA#
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key:  "19854336")#128B7114528B21A7E1B10746#)#D07929C9985AFBBF7C7DCEAFEC710B
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: D94812EBAA6420DCBCB60EE065356BF6B6351B8664AB4D4475F14C1752C6277FF0C6F7
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: FB24FC5E003CB67497D44076A0CAB22CFF6C3D7BF8E9FB5CF19919FBE6F756D8B96C22
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 9C0E0243928A7E4AFF23933EE0E786E783EBD3183A3988BCE7C68AEB8726C2AC2392E4
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 3C9DE81F97B7B99204D575145D9BE04E184A9186E66080E33532E68890BF13F19ACBB4
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 5E0E6C8865E950E5931C2A93D6D64A66016A10E7AC5EB05A6027A79D894F51F9CEFF41
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 696DA437CA4802D9BF1DD94A7CAEB61A6924AC57EBC1DC7ED4A1933A224D00A25ABD72
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 4ED848BD0D89155E77775C51B9FCEE06DF06D86E317CDBDED33887CD89690655F8F87A
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: DE5FBB854CEAE2B3ECDE525EA5C1A38EADBD85FBC825058C30EA73143BC5FEFF759798
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 0852FE5CEE4F0FE554E04A0055F2BB5AF3E823C70CF69D2CA298F37FB704A233B24696
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 1BCDB1F31D680B6C9E69529C619E37B44E74D300F3301BD931B3D60EEC1D80E951882C
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 9AD9378576B36C557349C17F4944583D85A0A69DCB0923DEDFA831331C2753D5BC8CF1
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: DA3CB494CE5BAEA39EBABFE5B2D55286E025B64A01AF2E66B9F4BE3D0001DF40F39604
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: F226D4BC385A15F44EF52008E32F15D91FFA50179F7CCB75E3FA2E851125D4B95B7CC0
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 6664BD0D5C53E641339D13B4808E7E6391CACFB585BABFEE6188BD2AE3CB535698256C
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: C42E095763CFDF2AFBC65802C8869F434A029EBA07F536CA6F5853B3494BFA64B8C213
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: C25A8F310EAAB726AC5C6C51878C18DF3BE16BA95F7DAD418A72F75E88CB2512C81A7A
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 659DB1D24AA718E29FBFC3CB01AB46BFFA7E560D025F67F0882A85DDE3BA858AD03E36
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 3D9BD05360215C839DDC9307D08772407A200F76939C56152FD2F3C2230099BB3DAA44
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 6042383AD2D85F9FE3B126EC1039ACF877F39FCD835D44001C2AFFDBDF56BE95171D7D
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: FBA13C702499BE9007A45F123675C01676ACB4EC5574760AF1330EDFADFE608B483EA7
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 3A5E8D293AB13FAA5AF48EC3262DB4CE6AAE5048A97D6827DD0D75D59FCE3F6E95C2BA
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: AECD106906BA86B623EBB4CE4744DCDC64E1F28D586572D217A40BD9DED7532835EC9E
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 8C9DDF4EF60EC24048A887F4573BE4BA6745E48DFA8C891AAB7EA4654751D634924DD7
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 4FB96BB84AFDE6F5033CA700466D257E4ECE7E6954679011FD21ED9169A30D41325F12
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 02FABC71E49487D1268315C49F9ECE579B9B024DE7ACD4079BE69CA55AEB4A420D32F9
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 659EC738F145C58DF87DF902B4036C8E755566FCECE7568FD95A73D873F09626CC79C0
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: 8DD05E122E7F9B6EEEBA30EEAE977CDD61F458ABF50DB9339527D02BFD2A586865B7DE
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: ED55B12A5FF0FD989C60DD9609C99D0122D501DAD6BF48018E98930B9F4C2D21A79DDB
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key: C4611A49ACAF1D93691CE164E42D8CD4AA21805C48FECB#)(protected-at
/etc/portage/gnupg/private-keys-v1.d/F2D25600836ACE50334B8C5CD6CD8CD4803C3714.key:  "20240821T185357")))
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key:Created: 20240821T185357
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key:Key: (protected-private-key (rsa (n #00F281763DB7F64FD936496BBAC7B7B509
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 73EB63DA661E327425BB03443342AFB697526969F338BAA8533CB8E522DC3830FF0F16
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 40AE7B9134DE2139E2D93C859D4B889A5C8D0A6C4D5B2AD3C3039D95FAE0226BB0A421
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 050B46459489930D1AB0AAB84BE324BA352FCD1BA1595AF882D8314124BA5A409AB16C
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 14CC5D500AA71041888F4B7C1B104A9B153EA65D6E56E40722B7EF36CBB0533147DFA0
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 3CDE32C0874FE46A6C524905BF707FF472BC2F93834A585746A46C0421650C9A609570
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: AF3AD456ABEA29427476F4B64ED561539CAB1B4FBCFA861F1DEF586C57D109F1D27CC7
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 6BB8591A6E2B6E01DF106E1098E47704FB3B2F40D96D68D4EA18BD8DE5D8915D254321
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 07A6DC43D5183AAF8BF0C8236D20B629A11AA602566547DE5080824D31571C9E2527FA
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 0C4D9F2143E8F09FB6B6B8FC32EF8AA4E1A3164EFF586EA42C4CD9CAC11AF09E352E33
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 74359248C95AD69D031FEF4F65B94748FF1B3D74D4A0DFB7E35E052B28E5A6018768E6
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 16A6EA30C263BBE95308C0D58D3347F3CE83#)(e #010001#)(protected
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key:  openpgp-s2k3-ocb-aes ((sha1 #4A1A225DA3BF1705#
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key:  "19854336")#687E951F03D4F3382E54DC96#)#ED0680B84FE0BB7E23072685D7F465
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: A4282AAF1937B81022C0AE958E976BA03D1AC8F25CCE31D75D7C4C1BC064537D9C2580
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 60A9AE0848EF41B29F8DD1FEC4EB78E1203570611EF5EECAB2BC04D927C79880CB1D28
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: C0E1DEAE5C67E0686D39AD2D904F3F24DFDD48D4C92844E11DB4CF178A6A5BFCFC0CAD
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 8C59748F3941F1B55D9BD6C5C8FE48B5438B641410C119A7A438DF78CD13E515D3A1DC
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 5FCD6AF118B81C66D5321DCD288C7BE514692A6A914F0C9C542228E7503A293896196E
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: F2ACC9984718A6A381E104796AE966110B5E602D7E2CE0D711ACA35822974C3F7D14F9
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: F669223200A5BAAEAF3EEA077A5DE599DB9007315F33E816A5ECAFA8E61052D0B1B57B
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 699C5C5939519C095D6FD01F177C70975F62AC52FF9456E8DC588DB223E356EDEEC0C2
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: D8B5FC824F4DC9D5E91FA10D4BD2950AE21FC114325E3156855DBF2E179DD5C1A2378A
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 4C4822E3DDEFF62C8355D500E1472696419315E916E5D9FE1A1FC6B0E9F34FE96E97D3
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 205547319C555DF8BF27C3C7A5FA51461AC995FA6D517797C7949C1ECA138072B72360
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 5E0A2B265ABCA56624A3C002838A1F9D834D6E2E6E9C10F93B90910C25822BC9E02DFD
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: BA18D656E66E947B93A57C41ADEDE2E40B59085B9A5FD60912D69A85FF830513B69159
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: C4C9265CFC73466EBB0BD9396E3847479B3F3B8B8D1B1AD8ECFC5E3422984955AFAFA4
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: A2A04821621D94A66D8FD3B1E5CEE3D8261A3DEFAD8748BFC485561AE3F7D2E72E5F43
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 1EBCF84C1D6C801D2F8E3B97B36B2EAD65EF405CD382137DD0004C493C8DAE997EF5A0
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 313EC3224F72FDFC3E322541214B9F8E15C00D8052EFA9BE0F2630289479C404A4D90F
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: B3CB9D7799DD9FF77DCF4CEDBB1AE7DA731E173C93926AA8918201528FC1DCA16B1F07
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 708DDDC0E657A6E9753813945A280580ACE6F046A4A21A2FF79537A8491F02246B8FF9
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: FFCDDEF4E99A7BF0C4C96E5991174E271BA3AB58AB4B175EE2B20A1143675654383A1C
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 7BABCCB094F0ED685089A527E1C35E25CB46C8B69B4ECA03E6247C57DB1BC13FBB143D
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 007D36F230886537A4F8CD25BEC62C1815F05C0FECB7CDE8AC20D271E9343B383636DF
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 13EE6BDE8EB36472DDEDE1AB1A535B69BC8DA1CB1A2B6BD88E6F14C4408A101B68FC2B
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 86FCDF4BD518BB10E75EA7D0E5DB49B8D55D744BD509F1FB1813AB866BCB2370CE8F91
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 58CD5498B6DA6F422D68EDADAE337BC3CA506E7E3BC0B36E6D234F4E352CF2A6C64125
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: 036BB3D701D32D0A4BFEAB60787AAC0079A38CF6F5540DEC53CDD744A94306ABB1BFE0
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: CF23BCED16B571FA54E315439F93CBF82EB458ED269FC643DF1C540212DA8F43B100EC
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: ACE8F50E6C231DFA90AECF0CBBAEF0F2207D0C7A870F984C38807A5E6D89A84DD258FE
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key: C73BF50F2BB3823E85DCE9663C78D54558526C8F3D117F#)(protected-at
/etc/portage/gnupg/private-keys-v1.d/3E7CF06BABA3A54D961559A396EDB4FE8E36D4DA.key:  "20240821T185358")))
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:This is a revocation certificate for the OpenPGP key:
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:pub   rsa3072 2024-08-21 [SCEAR]
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:      3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:uid          Portage Local Trust Key (local signing only) <portage@localhost>
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:A revocation certificate is a kind of "kill switch" to publicly
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:declare that a key shall not anymore be used.  It is not possible
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:to retract such a revocation certificate once it has been published.
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:Use it to revoke this key in case of a compromise or loss of
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:the secret key.  However, if the secret key is still accessible,
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:it is better to generate a new revocation certificate and give
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:a reason for the revocation.  For details see the description of
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:of the gpg command "--generate-revocation" in the GnuPG manual.
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:To avoid an accidental use of this file, a colon has been inserted
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:before the 5 dashes below.  Remove this colon with a text editor
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:before importing and publishing this revocation certificate.
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev::-----BEGIN PGP PUBLIC KEY BLOCK-----
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:Comment: This is a revocation certificate
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:iQG2BCABCAAgFiEEP7Ta4IIMhzpmAJ+au61RNLT226wFAmbGN8YCHQAACgkQu61R
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:NLT226z1dgv+O6pnUp6dPcficEPe9RVVVcHxnW1gD3qqVo9sgTHk/QfBOBZRRrl3
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:QxkEAtAsUY/04wr3WDUavt4MMnJNTkoCOeTjjdC23dQuIoPAOfGELjSp9ZYmjXky
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:fMyexo1jSOarzfmcFhTM6QA9lDZWiZdERHXro49bjPi3tJWeAHW90shxl2VkkDyd
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:+X5APDvFQX0df2FIWGyARoWC1EH05LVUoQ8wrweXcc90SJRNEiKxlDu7NM4G3eQT
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:GUezj44HxrYPWVBaf8m/ZqllJlbKJi/RLqY1p+k1SBUgh+IgyOC8z/fQUzDOoLJ/
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:5S2lPioUimxdE+almp/jq2oP+QCbZuJ2vItlc7xwFw8EfYLvogF46eC1RqeivK35
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:Jy6BQhLFr2VgyWtwd2eBSn5INDMJjymvHUe5c7gKcKK+a5PbIzXzKlX/nHNlhZJC
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:OqysapXRAnPftXgFsHa5xiiWSVdGUIzT1CSi90U9ryZGtafkjiG6VxfG2VJsQ3XO
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:Fn7ayxfkuLDU
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:=mH4+
/etc/portage/gnupg/openpgp-revocs.d/3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC.rev:-----END PGP PUBLIC KEY BLOCK-----
/etc/portage/gnupg/pass:Q/KFu8IEr1RFDvK8dr7t7AllHE4BOZ57VsiDXi0ka0s=
/etc/portage/gnupg/mykeyid:3FB4DAE0820C873A66009F9ABBAD5134B4F6DBAC
/etc/portage/gnupg/mykeyid:7FEE3FCE0E330A01A937608E560E669C23E783EB
/etc/portage/gnupg/crls.d/DIR.txt:v:1:
/etc/portage/make.conf:# These settings were set by the catalyst build script that automatically
/etc/portage/make.conf:# built this stage.
/etc/portage/make.conf:# Please consult /usr/share/portage/config/make.conf.example for a more
/etc/portage/make.conf:# detailed example.
/etc/portage/make.conf:COMMON_FLAGS="-march=haswell -O2 -pipe"
/etc/portage/make.conf:CFLAGS="${COMMON_FLAGS}"
/etc/portage/make.conf:CXXFLAGS="${COMMON_FLAGS}"
/etc/portage/make.conf:FCFLAGS="${COMMON_FLAGS}"
/etc/portage/make.conf:FFLAGS="${COMMON_FLAGS}"
/etc/portage/make.conf:
/etc/portage/make.conf:# NOTE: This stage was built with the bindist USE flag enabled
/etc/portage/make.conf:
/etc/portage/make.conf:# This sets the language of build output to English.
/etc/portage/make.conf:# Please keep this setting intact when reporting bugs.
/etc/portage/make.conf:LC_MESSAGES=C.utf8
/etc/portage/make.conf:
/etc/portage/make.conf:FEATURES="${FEATURES} getbinpkg buildpkg"
/etc/portage/make.conf:
/etc/portage/make.conf:VIDEO_CARDS="vmware"
/etc/portage/make.conf:
/etc/portage/make.conf:ACCEPT_LICENSE="-* @FREE @BINARY-REDISTRIBUTABLE"
/etc/portage/package.licence/kernel:app-arch/unrar unRAR
/etc/portage/package.licence/kernel:sys-kernel/linux-firmware linux-fw-redistributable
/etc/portage/package.licence/kernel:sys-firmware/intel-microcode intel-ucode
/etc/portage/package.licence/kernel:
Back to top
View user's profile Send private message
pietinger
Moderator
Moderator


Joined: 17 Oct 2006
Posts: 5161
Location: Bavaria

PostPosted: Thu Aug 22, 2024 10:31 am    Post subject: Re: Optimizing install-time settings to use binary host Reply with quote

lars_the_bear,

I can see that you are running Gentoo in a VM, using an 4 Core CPU with Intel Hyperthreading (means 8 logical cores) and you have given 9 GB RAM to this VM ...

lars_the_bear wrote:
[...] and routine updates are taking 2-3 days at 100% CPU.

... Yes, portage uses all 8 logical cores if you dont specify another value ... and yes, this is too much for 9 GB RAM ! I strongly recommend to set this into your /etc/portage/make.conf:
Code:
MAKEOPTS="-j3"

With this you should be able to work even when you do an "emerge -uUDv @world". If you would spend more RAM to this VM, you might use a higher value (e.g. 4 or 5) ... but please read:
https://wiki.gentoo.org/wiki/User:Pietinger/Tutorials/Optimize_compile_times
Dont be surprised if your emerge runs now FASTER than before ... because there will be no swapping with this setting :lol:

lars_the_bear wrote:
[...] And it was suggested that I should just set no USE flags at all. So I tried this. I set up a new installation and chose profile 23 'desktop/stable'. I didn't change any USE settings from their profile defaults at all.

But still everything wants to compile. Everything seems to want +pulseaudio and +wayland (at least), neither of which are set in this profile. These settings seem almost ubiquitous.

Yes, our pre-compiled packages use Use-flags you will only get if you set one of these profiles:
Code:
[25]  default/linux/amd64/23.0/desktop/gnome (stable)
...
[27]  default/linux/amd64/23.0/desktop/plasma (stable)

Please dont worry ... this profile will NOT INSTALL a Gnome (or KDE) system ... NO, only prerequisites ... and this profile will set automatically all necessary use-flags (e.g. wayland and pulse-audio).

You can check it - without doing any harm to your system - by setting it (eselect profile set 25) and doing an "emerge -info" ... Look at the line "USE= ...".

Now do a "emerge -uUDvp @world" (the -p is imporatant, so it does not start). You will see now some additionally packages ... but these you should get as binary ...
_________________
https://wiki.gentoo.org/wiki/User:Pietinger
Back to top
View user's profile Send private message
pietinger
Moderator
Moderator


Joined: 17 Oct 2006
Posts: 5161
Location: Bavaria

PostPosted: Thu Aug 22, 2024 10:48 am    Post subject: Reply with quote

P.S.: Sorry, I have not looked closely ...

Please do a:
Code:
ld.so --help

You should get something like this (at the end of the output):
Code:
[...]
Subdirectories of glibc-hwcaps directories, in priority order:
  x86-64-v4
  x86-64-v3 (supported, searched)
  x86-64-v2 (supported, searched)

Now take the highest value which is supported and change in your make.conf to (EXAMPLE):
Code:
COMMON_FLAGS="-march=x86-64-v3 -O2 -pipe"

_________________
https://wiki.gentoo.org/wiki/User:Pietinger
Back to top
View user's profile Send private message
lars_the_bear
Guru
Guru


Joined: 05 Jun 2024
Posts: 535

PostPosted: Thu Aug 22, 2024 11:10 am    Post subject: Reply with quote

@pietinger

Thank you. Please don't let me distract you with my VM settings -- I just set this one to test the effect of USE flags on compilation. I won't be using it for anything beyond that, and I didn't pay any attention to resource settings.

It would never have occurred to me in a million years to to use the profile

default/linux/amd64/23.0/desktop/gnome

if I didn't intend to run Gnome. I will try this, and see what happens.

When I was told that I would get most use of the binhost if I get to profile defaults, it wasn't clear to me that this only applies to certain profiles.

BR, Lars.
Back to top
View user's profile Send private message
pietinger
Moderator
Moderator


Joined: 17 Oct 2006
Posts: 5161
Location: Bavaria

PostPosted: Thu Aug 22, 2024 11:14 am    Post subject: Reply with quote

lars_the_bear wrote:
Thank you.

You are very Welcome ! :D

lars_the_bear wrote:
I will try this, and see what happens.

We all are always happy if we get a feedback ... if you have any problems please tell us, and you surely will get help.

Have fun with Gentoo ! 8)
_________________
https://wiki.gentoo.org/wiki/User:Pietinger
Back to top
View user's profile Send private message
lars_the_bear
Guru
Guru


Joined: 05 Jun 2024
Posts: 535

PostPosted: Thu Aug 22, 2024 2:56 pm    Post subject: Reply with quote

@pietinger

Thanks for you help, but I have to say that it doesn't really help, to use profile [25] (desktop/gnome) as an alternative to profile [23] (desktop).

Yes, I get more stuff supplied as binaries, which is what I wanted. But it creates a system that is designed to use pulseaudio. The ALSA configuration is set up as it is on Ubuntu, with 'pulse' as the default device. So, as a result, you have to be really careful to specify a particular ALSA device on everything that does audio. And some applications (e.g., firefox, so far as I can tell) don't even give you the option. Otherwise, pulseaudio gets started automatically, whether you want it or not. And when it's started, it seizes control of the ALSA devices.

And when I install Xfce4 ('emerge xfce4-meta), I get an installation of Xfce4 that is set up to use Pulse. So there's a panel applet for the Pulse mixer. So pulseaudio starts as soon as the desktop starts. I can fix this easily enough, just by removing the applet. I can also fix the ALSA configuration so it doesn't start pulseaudio, but it's a bit fiddly.

I've gone through this process with Ubuntu: I can remove Pulse, with some difficulty, but it comes back at the next update. I don't know if the same would be true for Gentoo.

In addition, when I install Xfce4, a colossal amount of Gnome stuff gets installed, including 'gnome-desktop'. I don't have to run it, so all it wastes is storage, but it's quite a lot of storage. With profile [23] (desktop), 'emerge xfce4-meta' installs something like 96 dependent packages. With profile [25] (desktop/gnome), it's over 200.

I really don't want to use Pulse. I have some applications -- some I wrote myself -- that work directly with ALSA, and Pulse breaks them. And even with applications that have specific Pulse support, it messages about with the audio streams.

There doesn't seem to be a way to use the Gentoo binhost to populate and maintain a really minimal system -- no Pulse, no Wayland, no Gnome stuff. But I'd love to find that I was just missing something.

BR, Lars.
Back to top
View user's profile Send private message
eschwartz
Developer
Developer


Joined: 29 Oct 2023
Posts: 238

PostPosted: Thu Aug 22, 2024 6:08 pm    Post subject: Re: Optimizing install-time settings to use binary host Reply with quote

lars_the_bear wrote:

In the earlier thread, @sam said:

Quote:
The binhost tries to stick to defaults on the profiles it builds for as much as possible (with some overlap between different profiles to cover common needs). Everything you configure (either enabling or disabling) is an additional constraint, whether you're using the binhost or not, and making use of the power to customise. By using that power, you then have to accept e.g. building more.


And it was suggested that I should just set no USE flags at all. So I tried this. I set up a new installation and chose profile 23 'desktop/stable'. I didn't change any USE settings from their profile defaults at all.

But still everything wants to compile. Everything seems to want +pulseaudio and +wayland (at least), neither of which are set in this profile. These settings seem almost ubiquitous.


From https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart#Profiles

Quote:

This binhost is built with USE flags of the following profiles:

default/linux/amd64/23.0/no-multilib
default/linux/amd64/23.0/desktop/gnome/systemd
default/linux/amd64/23.0/desktop/plasma/systemd

This will cover most of the USE flag combinations needed for both a OpenRC and systemd system.


23.0/desktop doesn't set "pulseaudio and wayland", but both 23.0desktop/gnome and 23.0/desktop/plasma do. However the "server" (23.0/no-multilib) binhost doesn't build qtwebengine in particular...
Back to top
View user's profile Send private message
eschwartz
Developer
Developer


Joined: 29 Oct 2023
Posts: 238

PostPosted: Thu Aug 22, 2024 6:15 pm    Post subject: Reply with quote

lars_the_bear wrote:


Thanks for you help, but I have to say that it doesn't really help, to use profile [25] (desktop/gnome) as an alternative to profile [23] (desktop).

Yes, I get more stuff supplied as binaries, which is what I wanted. But it creates a system that is designed to use pulseaudio. The ALSA configuration is set up as it is on Ubuntu, with 'pulse' as the default device. So, as a result, you have to be really careful to specify a particular ALSA device on everything that does audio. And some applications (e.g., firefox, so far as I can tell) don't even give you the option. Otherwise, pulseaudio gets started automatically, whether you want it or not. And when it's started, it seizes control of the ALSA devices.

And when I install Xfce4 ('emerge xfce4-meta), I get an installation of Xfce4 that is set up to use Pulse. So there's a panel applet for the Pulse mixer. So pulseaudio starts as soon as the desktop starts. I can fix this easily enough, just by removing the applet. I can also fix the ALSA configuration so it doesn't start pulseaudio, but it's a bit fiddly.

[...]

There doesn't seem to be a way to use the Gentoo binhost to populate and maintain a really minimal system -- no Pulse, no Wayland, no Gnome stuff. But I'd love to find that I was just missing something.


In this situation, like IIRC I said in a different thread, it probably makes more sense to use the regular "desktop" profile, not the gnome-specific one, and simply use package.use for specific packages.

Code:

$ cat /etc/portage/package.use/desktop
[...]

# binary
media-libs/mesa wayland
dev-qt/qtgui wayland
dev-qt/qtmultimedia pulseaudio qml
dev-qt/qttools qml
dev-qt/qtwebengine pulseaudio screencast qml
dev-qt/qtwebchannel qml
media-libs/libcanberra pulseaudio
media-libs/libvpx postproc
media-libs/freetype harfbuzz
dev-db/sqlite -icu


You don't have to build xfce4 with a pulseaudio panel and autostart setup, but as long as you're willing to install *libpulse* (not pulseaudio) you can install some binary packages compiled with libpulse support for ease of binary package usage without committing to a pulseaudio system.
Back to top
View user's profile Send private message
pjp
Administrator
Administrator


Joined: 16 Apr 2002
Posts: 20496

PostPosted: Thu Aug 22, 2024 6:40 pm    Post subject: Reply with quote

@lars_the_bear

The idea is that you install the binaries, then make USE changes. That will of course require you to build stuff. You can then evaluate what that is and if it helps any. Minimize what you want to eliminate. Support for wayland doesn't necessarily mean you have to use wayland. I presume that it also supports X, so you choose.

You won't get the minimal system you originally tried to make. The question is whether or not the compromise is acceptable. You've already ruled out other options. So if this too isn't an option, then you are left with pen and paper.
_________________
Quis separabit? Quo animo?
Back to top
View user's profile Send private message
lars_the_bear
Guru
Guru


Joined: 05 Jun 2024
Posts: 535

PostPosted: Thu Aug 22, 2024 7:15 pm    Post subject: Reply with quote

@eschwartz

Thank you. I'm trying to understand how you arrived at the `package.use/desktop` file (or snippet of file) you posted. Is it something you deduced, or is it just a matter of trying to install things, seeing what doesn't get a binary, and then tweaking until it does?

And if you do that, how do you know that you'll end up with components that actually work together? Or is it just a matter of trying it and seeing what happens?

For example, if I have

Code:

dev-qt/qtmultimedia pulseaudio ...


as you do, and I'm not using Pulse, is there a way to know these settings will work? Since I won't have installed qtmultimedia explicitly, but got it as some kind of dependency, how do I actually test it? I'm not sure how I would (a) find out what actually uses the dependency and then (b) find out whether it uses audio via qtmultimedia and then (c) find a way to test whether that software, whatever it is, does audio properly.

I'm sure if you've been using Gentoo for years this is all just painfully obvious. But it's making my head spin.

BR, Lars.
Back to top
View user's profile Send private message
lars_the_bear
Guru
Guru


Joined: 05 Jun 2024
Posts: 535

PostPosted: Thu Aug 22, 2024 7:17 pm    Post subject: Reply with quote

pjp wrote:
So if this too isn't an option, then you are left with pen and paper.


Or MS-DOS. There's a good article on Hackaday

https://hackaday.com/2024/08/22/running-stock-ms-dos-on-a-modern-thinkpad/

about a guy running DOS 6.22 on his Lenovo X13.

It seems odd to me, that Linux would be harder to make work effectively on an old Lenvo than DOS.

BR, Lars.
Back to top
View user's profile Send private message
eschwartz
Developer
Developer


Joined: 29 Oct 2023
Posts: 238

PostPosted: Thu Aug 22, 2024 7:35 pm    Post subject: Reply with quote

lars_the_bear wrote:
@eschwartz

Thank you. I'm trying to understand how you arrived at the `package.use/desktop` file (or snippet of file) you posted. Is it something you deduced, or is it just a matter of trying to install things, seeing what doesn't get a binary, and then tweaking until it does?


Usually, I copy/paste it from the output of emerge when it says "The following binary packages have been ignored due to non matching USE:" and suggests a possible modification.

lars_the_bear wrote:

And if you do that, how do you know that you'll end up with components that actually work together? Or is it just a matter of trying it and seeing what happens?

For example, if I have

Code:

dev-qt/qtmultimedia pulseaudio ...


as you do, and I'm not using Pulse, is there a way to know these settings will work? Since I won't have installed qtmultimedia explicitly, but got it as some kind of dependency, how do I actually test it? I'm not sure how I would (a) find out what actually uses the dependency and then (b) find out whether it uses audio via qtmultimedia and then (c) find a way to test whether that software, whatever it is, does audio properly.

I'm sure if you've been using Gentoo for years this is all just painfully obvious. But it's making my head spin.


I actually don't have qtmultimedia installed right now? Apparently I pulled it in at one time as a dependency for something else I was trying out.

Doesn't matter. Any possible combination of USE flags *should* be valid to get a working package, or if there is an incompatibility then the package should list it as REQUIRED_USE and refuse to continue stating that you need to better-specify your desired configuration.

The goal of the package.use is simply to ensure that

a) the USE flags you actually care about are set elsewhere and already being used

b) additional USE flags you don't care about, but are willing to tolerate for the sake of binary packages, are active as per this specific file

The settings work because adding libpulse support to qtmultimedia doesn't force it to use libpulse. If a package e.g. supported libpulse or alsa, but not both at the same time, then it would have both USE flags, in the form
Code:
REQUIRED_USE="^^ ( alsa pulseaudio )"
and you would be forced to pick exactly one of them -- if you set pulseaudio without setting -alsa then portage would log an error and refuse to continue until you picked one and *only* one.
Back to top
View user's profile Send private message
pietinger
Moderator
Moderator


Joined: 17 Oct 2006
Posts: 5161
Location: Bavaria

PostPosted: Thu Aug 22, 2024 7:37 pm    Post subject: Reply with quote

lars_the_bear,

you have a strong Skylake i7 ... and 9 GB RAM is really sufficient to compile all appliations.

I love to have also a minimal system (but I also love KDE) ... So I suggest go the (old) Gentoo way and dont use prebuild packages. If you use XFCE you really should have no problems getting a lot of packages,

Maybe change also your COMMON_FLAGS= to
Code:
COMMON_FLAGS="-march=native -O2 -pipe"

(I think "haswell" was wrong anyway.)
Dont forget to set MAKEOPTS="-j3"

So, the road could be:

1. Using gentoo-kernel-bin
2. Setting profile back to desktop
3. Unset everything you dont need (*)
4. Start an emerge world and go to bed (when your system uses only 3 logical cores out of 8 then there should be no overheating)


*) I am using a plasma-profile but I use also native ALSA (no pipewire, no pulseaudio ). In my make.conf I have more Use-flags deselected than enabled:
Code:
COMMON_FLAGS="-march=raptorlake -O2 -pipe"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
LC_MESSAGES=C
ACCEPT_LICENSE="* -@EULA"
MAKEOPTS="-j24"
L10N="de"
VIDEO_CARDS="intel"
USE="-accessibility -activities -bluetooth -gstreamer -gtk -gtk3 -haptic -initramfs -ipv6 -lvm -modemmanager -networkmanager -phonon -ppp -pulseaudio -screencast -semantic-desktop -thin -thumbnail -wext -wifi -wireless "
USE="$USE jumbo-build lm-sensors matroska openexr opus theora threads vaapi vpx webp"

(Don't be surprised that I have "raptorlake" instead of "native"; this is unfortunately necessary for CPUs that have P- and E-cores; "native" is better for you.)

together with some local flags:
Code:
$ more /etc/portage/package.use

*/* CPU_FLAGS_X86: aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sha sse sse2 sse3 sse4_1 sse4_2 ssse3 vpclmulqdq
net-misc/netifrc -dhcp
net-misc/chrony -nettle -nts -sechash
kde-plasma/plasma-meta -crypt -crash-handler
sys-apps/i2c-tools python
media-video/pipewire -sound-server
virtual/libcrypt static-libs
sys-libs/libxcrypt static-libs
sys-apps/busybox -pam static
net-firewall/iptables nftables

# temporary because of bug: https://bugs.gentoo.org/916267
>=dev-qt/qtgui-5.15.11-r2 accessibility

# temporary because of bug: https://bugs.gentoo.org/864721
media-video/vlc -vaapi

Yes, I use netifrc with a static IP address ... no dhcpcd, no networkmanager.
Yes, I dont use grub as bootmanager because I boot my manually configured kernel directly by UEFI. This means also I dont need "installkernel"
Yes, I use qtwebengine ... because I use Kmail,Konqueror,Falkon,Akregator and Marble (all 5 needs it) ... yes, qtwebengine is a monster ... but ... which mail application and browser do you use ? Thunderbird is a monster too ... I think it is a clever solution to have an external webengine ... emerging my 5 needed applications is done in a few minutes.


BTW:
lars_the_bear wrote:
[...] but got it as some kind of dependency, how do I actually test it? I'm not sure how I would (a) find out what actually uses the dependency [...]

Check it with "emerge -cpv PACKAGENAME" ... e.g.:
Code:
$ emerge -cpv qtwebengine

Calculating dependencies... done!
  dev-qt/qtwebengine-5.15.14_p20240510 pulled in by:
    app-office/merkuro-23.08.5 requires >=dev-qt/qtwebengine-5.15.9:5
    kde-apps/akregator-23.08.5 requires >=dev-qt/qtwebengine-5.15.9:5
    kde-apps/grantlee-editor-23.08.5 requires >=dev-qt/qtwebengine-5.15.9:5[widgets]
    kde-apps/kdepim-runtime-23.08.5 requires >=dev-qt/qtwebengine-5.15.9:5[widgets]
    kde-apps/kmail-23.08.5 requires >=dev-qt/qtwebengine-5.15.9:5[widgets]
    kde-apps/konqueror-23.08.5-r1 requires >=dev-qt/qtwebengine-5.15.9:5[widgets]
    kde-apps/kontact-23.08.5 requires >=dev-qt/qtwebengine-5.15.9:5[widgets]
    kde-apps/libksieve-23.08.5 requires >=dev-qt/qtwebengine-5.15.9:5[widgets]
    kde-apps/marble-24.05.2 requires >=dev-qt/qtwebengine-5.15.12:5[widgets]
    kde-apps/messagelib-23.08.5 requires >=dev-qt/qtwebengine-5.15.9:5[widgets]
    www-client/falkon-23.08.5 requires >=dev-qt/qtwebengine-5.15.9:5=[widgets], >=dev-qt/qtwebengine-5.15.9:5/5.15=[widgets]

_________________
https://wiki.gentoo.org/wiki/User:Pietinger


Last edited by pietinger on Thu Aug 22, 2024 7:43 pm; edited 1 time in total
Back to top
View user's profile Send private message
pjp
Administrator
Administrator


Joined: 16 Apr 2002
Posts: 20496

PostPosted: Thu Aug 22, 2024 7:42 pm    Post subject: Reply with quote

lars_the_bear wrote:
It seems odd to me, that Linux would be harder to make work effectively on an old Lenvo than DOS.
If DOS "works" then sure. I never liked it and was glad to be rid of it.

What's partly amusing about your old hardware issue isn't the age, rather it's form factor. Your hardware is probably more capable than the PC I use to build binaries, but my system has better cooling by definition of it not being a laptop. It's really a shame you can't get a PC on which to make the binaries, one possibly even older than the laptops.

But as far as I can tell, you haven't even tried to actually use the Gentoo binaries yet, just decided it doesn't work. Which is fine.
_________________
Quis separabit? Quo animo?
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 22729

PostPosted: Thu Aug 22, 2024 7:58 pm    Post subject: Reply with quote

I expect that getting a Linux that works as well as DOS, and no better, isn't that hard on old hardware. DOS sets the bar so low that it is easy to reach. DOS had no built-in networking, so you have minimal need for a browser or mail client on this hypothetical Linux. DOS had no built-in WIMP system (that was what Windows was for), so no need for X11 or Wayland. DOS predated both 64-bit CPUs and systems where 32-bit addressing was insufficient to cover all of RAM, so you can use a no-PAE 32-bit Linux kernel.
Back to top
View user's profile Send private message
pjp
Administrator
Administrator


Joined: 16 Apr 2002
Posts: 20496

PostPosted: Thu Aug 22, 2024 9:30 pm    Post subject: Reply with quote

I'd probably go with TempleOS. If I recall, it had some games. Holy C alone might be worth it.
_________________
Quis separabit? Quo animo?
Back to top
View user's profile Send private message
lars_the_bear
Guru
Guru


Joined: 05 Jun 2024
Posts: 535

PostPosted: Fri Aug 23, 2024 8:06 am    Post subject: Reply with quote

pjp wrote:

But as far as I can tell, you haven't even tried to actually use the Gentoo binaries yet, just decided it doesn't work. Which is fine.


That's not true. I've tried -- I've tried very hard, over several months. I just can't get binaries that match the USE and CPU flag settings I have. I chose a profile that excludes Pulse and Wayland, and most binaries seem to expect these things to be enabled.

I tried using the desktop/gnome profile, and that got me all the binaries -- but it also got me a load of Gnome that I really don't want. And Pulse, which I really, really don't want.

I understand from the preceding discussion that I might be able to enabled USE settings on a package-by-package basis and hope/test that this still works.

Honestly, all I want is to use Linux on my old-ish laptop and have it work as well and with as little hassle as it did in 2014. When I naively embarked on this effort, this didn't seem like an unworthy or unreasonable goal. I'm not seriously thinking about going back to DOS but, frankly, I'd go back to Windows 7 if it wasn't such a security risk. That old laptop worked great with Windows 7 and, with Cygwin and MinGW it was a serviceable development platform.

I'd rather use Linux; it's just disheartening how difficult it seems to be.

BR, Lars.
Back to top
View user's profile Send private message
flysideways
Guru
Guru


Joined: 29 Jan 2005
Posts: 494

PostPosted: Fri Aug 23, 2024 3:33 pm    Post subject: Re: Optimizing install-time settings to use binary host Reply with quote

lars_the_bear wrote:
My computers are not fast at compiling, and routine updates are taking 2-3 days at 100% CPU.


Have you actually installed to bare metal, or is all of your Gentoo experience in VM's?

I have read a few of your threads. I have been running compiled Gentoo on Pi's, which also are performance constrained, so I have a good feel for updates and how long they take.

When you mention "routine" updates, I have to ask, what is the frequency? Is it once a month? Is it once a week? I have been in a once a month update cycle for a while on my Pi's. That frequency lends to a long emerge. Once a week, and only occasionally does it go beyond a day. That is with a Gnome desktop install. With a Pi 4 and XFCE, I'd swear an emerge --emptytree (rebuilds everything) was 19 hours.

I also thought you mentioned more than one laptop in one of the threads. Depending how you intend to use them, if one is used less than the other, maybe use that one for compiling and your own local binhost for the other?

You can also use distcc to share the compile load across more than one computer.
Back to top
View user's profile Send private message
pjp
Administrator
Administrator


Joined: 16 Apr 2002
Posts: 20496

PostPosted: Sat Aug 24, 2024 4:25 am    Post subject: Reply with quote

lars_the_bear wrote:
That's not true. I've tried -- I've tried very hard, over several months. I just can't get binaries that match the USE and CPU flag settings I have. I chose a profile that excludes Pulse and Wayland, and most binaries seem to expect these things to be enabled.
My apologies. I should have been more specific. I don't dispute your past efforts. I was specifically referring to the idea in this thread about using settings that worked with Gentoo built binaries.

Based on your preferences, the only remaining option appeared to be compromising on what you could install or choose to not install. Thus, use Gentoo's binaries and slowly try to eliminate some of the things you don't want, realizing that you can't have everything, given your preferences.

So when I wrote that I didn't think you'd tried yet, I was specifically referring to that scenario, and I believed it to be accurate based on when you wrote this:
lars_the_bear wrote:
don't let me distract you with my VM settings -- I just set this one to test the effect of USE flags on compilation. won't be using it for anything beyond that
I read that to mean you were only looking at the output from within the VM to determine that you couldn't get the exact specific thing you want, and had not yet tried to install the binaries to see what compromises you had to make.

lars_the_bear wrote:
I tried using the desktop/gnome profile, and that got me all the binaries -- but it also got me a load of Gnome that I really don't want. And Pulse, which I really, really don't want.
It seems to me that it would be a lot easier if you installed it, then slowly tried to back away from things. Also understand that software including support may not necessarily mean you have to use it.

lars_the_bear wrote:
I understand from the preceding discussion that I might be able to enabled USE settings on a package-by-package basis and hope/test that this still works.
That is how it works.

lars_the_bear wrote:
Honestly, all I want is to use Linux on my old-ish laptop and have it work as well and with as little hassle as it did in 2014.
It isn't 2014, so that's almost certainly not going to happen,. Accept that you might be able to do something pre-2024, and you'll only know that that looks like when you get there (or decide it isn't worth the journey).

lars_the_bear wrote:
When I naively embarked on this effort, this didn't seem like an unworthy or unreasonable goal. I'm not seriously thinking about going back to DOS but, frankly, I'd go back to Windows 7 if it wasn't such a security risk. That old laptop worked great with Windows 7 and, with Cygwin and MinGW it was a serviceable development platform.

I'd rather use Linux; it's just disheartening how difficult it seems to be.
It's not difficult at all, even on your hardware. The difficulty comes with your apparent unwillingness to accept that you'll have to make compromises.

Do what you will, of course, but I'd try to forget about the ideal you want and instead slowly try to peel back the pieces and discover how close you can get to it.

And I'd be remiss if I didn't also add that you keep an eye out for a used, cheap (or even free) PC that has better cooling for only occasional use on some of the things you'd like to have. That solves most of your issues. You get to use the old hardware, including such a PC.

Good luck!
_________________
Quis separabit? Quo animo?
Back to top
View user's profile Send private message
lars_the_bear
Guru
Guru


Joined: 05 Jun 2024
Posts: 535

PostPosted: Sat Aug 24, 2024 7:15 am    Post subject: Reply with quote

pjp wrote:
The difficulty comes with your apparent unwillingness to accept that you'll have to make compromises.


What compromises have I not accepted? The only thing I can't compromise on is Pulse/Pipewire -- I can't run these things because they interfere with software that I use, and because they mess about with the audio. In all other respects, I'm willing to compromise.

I need to arrive at a point where I can run FreeCAD, KiCAD, and Darktable. I don't really care how I get there. All are memory-hogging monsters. I've assumed, in order to get to a point where these things work, I need to eliminate everything that uses memory for avoidable reasons. I've found that they will all run reasonably well in 16Gb RAM, provided nothing much else is competing for the RAM.

My experience so far is that, to get to that working system, I have to make tuning settings that lead to endless compilation every time I update. Nothing I've tried so far has changed that. I've tried many suggestions that folks have made on this forum, and the results have so far always been that to reduce compilation, I have to accept a system configured to run more processes (generally including Pulse).

I'm willing to accept that my lack of success is due to my lack of knowledge but, with that one exception, I don't think it's my unwillingness to compromise.

BR, Lars.
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 22729

PostPosted: Sat Aug 24, 2024 2:20 pm    Post subject: Reply with quote

lars_the_bear wrote:
pjp wrote:
The difficulty comes with your apparent unwillingness to accept that you'll have to make compromises.
What compromises have I not accepted?
From memory of your past posts:
  • You won't run GNOME. (I sympathize. The last time I tried to deal with GNOME, I hated so many UI decisions (some defaults, some just outright missing functionality) that I decided to find a non-GNOME system rather than try to customize it to work like I wanted.)
  • You won't allow installation of Pulseaudio / Pipewire.
  • You won't commit to hardware suitable for locally building large software.
  • You won't commit to not using large software.
lars_the_bear wrote:
The only thing I can't compromise on is Pulse/Pipewire -- I can't run these things because they interfere with software that I use, and because they mess about with the audio.
I see two problems with this line of reasoning.
  1. Do they absolutely break that software, or are they an inconvenience that requires you to configure around it? If they only need to be configured, you might spend less effort getting them to behave than you have spent and are continuing to spend trying to avoid them.
  2. You seem to be conflating running them with installing them. Various posters have asserted that many packages with optional Pulseaudio / Pipewire support can have that enabled at compile-time (via USE flag), but not used at run time. Have you explored allowing Pulseaudio / Pipewire to be installed, but then ensuring they never run?
lars_the_bear wrote:
In all other respects, I'm willing to compromise.
Are you willing to compromise on obtaining hardware fit for purpose? Are you willing to compromise on not running memory intensive software?
lars_the_bear wrote:
I need to arrive at a point where I can run FreeCAD, KiCAD, and Darktable. I don't really care how I get there. All are memory-hogging monsters. I've assumed, in order to get to a point where these things work, I need to eliminate everything that uses memory for avoidable reasons. I've found that they will all run reasonably well in 16Gb RAM, provided nothing much else is competing for the RAM.
Do you need to run them all concurrently, or is it sufficient to run one, exit it, and start another? Is that 16Gb figure for concurrent use or serial use? Is their memory use pattern such that a large swap device makes a meaningful difference? Some programs have a large footprint, but most of it can be swapped out. Others access their memory in a way that you need to keep most of it resident in RAM to avoid painfully slow swap thrashing.
lars_the_bear wrote:
My experience so far is that, to get to that working system, I have to make tuning settings that lead to endless compilation every time I update. Nothing I've tried so far has changed that. I've tried many suggestions that folks have made on this forum, and the results have so far always been that to reduce compilation, I have to accept a system configured to run more processes (generally including Pulse).
Maybe what you want is impossible. Maybe not.

This thread seems to be about ensuring you get the most use of the binhost. The above paragraph suggests to me that you got a good level of use out of it, and were unhappy with the resulting system. Do you want to continue pursuing use of the binhost, even when that requires deeper compromises on what you install, or do you want to go back to using the binhost less, and trying to compromise on what you build?
Back to top
View user's profile Send private message
eschwartz
Developer
Developer


Joined: 29 Oct 2023
Posts: 238

PostPosted: Sun Aug 25, 2024 4:01 am    Post subject: Reply with quote

Gonna reiterate again that there are two entirely different packages:

- libpulse, provides library APIs which projects that support pulseadio need to have available due to link requirements, in order that said projects can implement "if pulseaudio is running, interact with it"

- pulseaudio-daemon, a sound server daemon


If we look at qtwebengine, for example, here is its dependency:

pulseaudio? ( media-libs/libpulse[glib] )

Note, it depends on libpulse, not the daemon. You can compile qtwebengine with runtime-switchable support for pulseaudio, and the binhost does, but all that means is installing the libpulse support libraries. You aren't forced to *use* pulseaudio, and you aren't even forced to *install* it -- just to install the support libraries. Although either way, nothing forces you to *run* it.

Using prebuilt binaries for convenience, adds *installation dependencies* on libpulse, it does not force you to actually use pulseaudio-daemon. This is the same reason why most binary distros tend to compile with libpulse support as the only option, even though they do allow you to run alsa or pulseaudio as you please.
Back to top
View user's profile Send private message
lars_the_bear
Guru
Guru


Joined: 05 Jun 2024
Posts: 535

PostPosted: Sun Aug 25, 2024 6:32 pm    Post subject: Reply with quote

eschwartz wrote:

Using prebuilt binaries for convenience, adds *installation dependencies* on libpulse, it does not force you to actually use pulseaudio-daemon. This is the same reason why most binary distros tend to compile with libpulse support as the only option, even though they do allow you to run alsa or pulseaudio as you please.


I simply followed the advice given to me on this forum, and set up a system with the profile 'desktop/gnome', rather than 'desktop' I had been using. While this did increase the amount of binary packages I used, it didn't just create a system with Pulse capability -- it created a system that ran pulseaudio, whether I wanted it or not.

The ALSA set-up had 'pulse' as the default device. Using this devices starts the pulseaudio server. In addition, even Xfce4 was set up to start pulseaudio when the desktop starts.

So far as I can tell, using this profile did not merely provide Pulse support, but created a systems with Pulse set up in a way that was difficult to avoid.

I understand that it might be possible to use USE=pulseaudio selectively on some packages, to allow the binary to be used, and that won't (necessarily) force the use of Pulse. Trying this is on my to-do list, but it will take some time.

BR, Lars.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
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