View previous topic :: View next topic |
Author |
Message |
hunky l33t
Joined: 19 Nov 2003 Posts: 912 Location: Alaska
|
Posted: Tue Mar 26, 2024 6:23 am Post subject: profile 23 - ignored packages non matching use |
|
|
Going thru the steps on what was a 17.1 amd64 desktop plasma non-systemd system and got to the emerge world empty tree command and I get a bunch of ignored packages (lots have systemd USE which I hope to avoid where I can). I have gone thru my package.use file to make sure I don't have duplicates of any of these files in there (been using gentoo a long time).
Should I proceed regardless these ignored packages or is there something I should do to fix it? I haven't a clue why some of these are duplicated - some more than once.
Code: | !!! The following binary packages have been ignored due to non matching USE:
=sys-apps/baselayout-2.14-r2 -split-usr
=app-alternatives/awk-4 -split-usr
=app-alternatives/bzip2-1 -split-usr
=app-alternatives/gzip-1 -split-usr
=app-alternatives/tar-0 -split-usr
=app-arch/bzip2-1.0.8-r5 -static-libs
=app-arch/xz-utils-5.6.1 -static-libs
=app-arch/xz-utils-5.6.1 -abi_x86_32 -static-libs
=net-misc/wget-1.21.4 -gnutls
=sys-apps/coreutils-9.4-r1 -split-usr
=sys-apps/shadow-4.14.2 -split-usr
=sys-apps/shadow-4.14.2 -split-usr systemd
=sys-apps/util-linux-2.39.3-r2 -abi_x86_32 -udev
=sys-apps/util-linux-2.39.3-r2 -abi_x86_32
=sys-apps/util-linux-2.39.3-r2 -abi_x86_32 systemd
=sys-devel/gcc-13.2.1_p20240210 -graphite -multilib -objc
=sys-devel/gcc-13.2.1_p20240210 -graphite -objc
=sys-process/procps-3.3.17-r2 -elogind -split-usr systemd
=sys-process/procps-3.3.17-r2 -split-usr
=sys-process/procps-3.3.17-r2 -elogind -split-usr
=app-arch/p7zip-16.02-r8 -kde -wxwidgets
=app-arch/rpm-4.18.1 -dbus
=app-text/evince-45.0 gnome gstreamer keyring
=kde-apps/kdecore-meta-23.08.5 webengine
=kde-apps/kdenlive-23.08.5 -v4l
=kde-apps/kdenlive-23.08.5 -semantic-desktop -v4l
=kde-apps/kdeutils-meta-23.08.5 webengine
=kde-apps/kdeutils-meta-23.08.5 -plasma webengine
=kde-plasma/plasma-meta-5.27.11 -colord -elogind firewall gtk systemd
=kde-plasma/plasma-meta-5.27.11 gtk
=media-video/ffmpeg-6.0.1-r4 cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_fma3 cpu_flags_x86_sse3 cpu_flags_x86_sse4_1 cpu_flags_x86_sse4_2 cpu_flags_x86_ssse3 -fdk -ieee1394 -jack -ladspa -libass -openssl opus -samba -v4l -x265
=media-video/ffmpeg-6.0.1-r4 cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_fma3 cpu_flags_x86_sse3 cpu_flags_x86_sse4_1 cpu_flags_x86_sse4_2 cpu_flags_x86_ssse3 -fdk -ieee1394 -jack -ladspa -openssl -samba -theora -v4l -vpx -x265
=media-video/ffmpeg-6.0.1-r4 cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_fma3 cpu_flags_x86_sse3 cpu_flags_x86_sse4_1 cpu_flags_x86_sse4_2 cpu_flags_x86_ssse3 -fdk -ieee1394 -jack -ladspa -openssl opus -samba -v4l -x265
=media-video/mpv-0.37.0 -dvb -jack
=media-video/mpv-0.37.0 -dvb -jack -pipewire
=media-video/pipewire-1.0.3 -doc -echo-cancel -extra -ffmpeg -flatpak gstreamer -ieee1394 -sound-server systemd -v4l
=media-video/pipewire-1.0.3 -doc -echo-cancel -extra -ffmpeg -flatpak -ieee1394 systemd -v4l
=media-video/pipewire-1.0.3 -doc -echo-cancel -extra -ffmpeg -flatpak gstreamer -ieee1394 -sound-server -v4l
=media-video/vlc-3.0.20-r5 -cddb gstreamer -ieee1394 -jack keyring -matroska -mtp -nfs -opus -samba -taglib -theora -v4l
=media-video/vlc-3.0.20-r5 -cddb -ieee1394 -jack -matroska -mtp -nfs -opus -samba -taglib -theora -v4l
=net-print/cups-2.4.7-r2 usb
=net-print/cups-2.4.7-r2 systemd usb
=www-client/lynx-2.9.0_pre12-r1 -gnutls
=x11-apps/xdpyinfo-1.3.4 -xinerama
=x11-base/xorg-drivers-21.1-r2 -input_devices_evdev input_devices_libinput video_cards_dummy video_cards_fbdev video_cards_intel video_cards_nouveau video_cards_radeon video_cards_vesa
=sys-devel/gettext-0.22.4 -java
=sys-libs/glibc-2.38-r10 -gd systemd
=sys-libs/glibc-2.38-r10 -gd
=sys-libs/glibc-2.38-r10 -gd -multilib -stack-realign
=sys-libs/zlib-1.3-r4 -abi_x86_32 -minizip -static-libs
=sys-libs/zlib-1.3-r4 -static-libs
=sys-libs/zlib-1.3-r4 -abi_x86_32 -static-libs
=dev-libs/glib-2.78.3 -abi_x86_32
=dev-libs/glib-2.78.3 -abi_x86_32 sysprof
=dev-libs/glib-2.78.3 -abi_x86_32 -dbus
=dev-lang/python-3.11.8_p1 -bluetooth
=sys-libs/ncurses-6.4_p20230401 gpm -split-usr
=sys-libs/ncurses-6.4_p20230401 abi_x86_32 -split-usr
=sys-libs/ncurses-6.4_p20230401 -split-usr -stack-realign
=dev-db/sqlite-3.45.1-r1 -icu -secure-delete
=dev-db/sqlite-3.45.1-r1 -secure-delete
=sys-apps/dbus-1.15.8 -abi_x86_32 -elogind systemd
=sys-apps/dbus-1.15.8 -abi_x86_32
=x11-libs/libX11-1.8.7 -abi_x86_32
=dev-libs/libgcrypt-1.10.3-r1 cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_sse4_1
=sys-libs/libcap-2.69-r1 -abi_x86_32
=sys-libs/pam-1.5.3-r1 -abi_x86_32
=sys-auth/polkit-123 gtk -kde systemd
=sys-auth/polkit-123 gtk systemd
=sys-auth/polkit-123 gtk -kde
=sys-auth/pambase-20240128 -elogind gnome-keyring systemd
=sys-auth/pambase-20240128 -elogind systemd
=sys-auth/pambase-20240128 gnome-keyring
=sys-auth/pambase-20240128 -elogind
=dev-qt/qtwidgets-5.15.12-r1 gtk
=dev-libs/libpcre2-10.42-r2 -abi_x86_32
=x11-libs/libXext-1.3.6 -abi_x86_32
=x11-libs/libXfixes-6.0.1 -abi_x86_32
=app-arch/zstd-1.5.5-r1 abi_x86_32 -static-libs
=app-arch/zstd-1.5.5-r1 -static-libs
=app-accessibility/at-spi2-core-2.50.1 -abi_x86_32 systemd
=app-accessibility/at-spi2-core-2.50.1 -abi_x86_32
=dev-libs/lzo-2.10 -split-usr
=x11-libs/pixman-0.43.2 cpu_flags_x86_ssse3
=net-misc/curl-8.6.0-r1 -gnutls -samba
=x11-libs/gtk+-3.24.39 sysprof -xinerama
=x11-libs/gtk+-3.24.39 -colord -xinerama
=media-libs/mesa-23.3.6 video_cards_intel video_cards_nouveau video_cards_radeon
=x11-libs/libdrm-2.4.120 video_cards_intel video_cards_nouveau
=dev-libs/libbsd-0.11.8 -abi_x86_32
=dev-libs/nss-3.91 cpu_flags_x86_avx2 cpu_flags_x86_sse3
=dev-libs/boehm-gc-8.2.4 -cxx
=media-libs/libpulse-17.0 gtk systemd
=media-libs/libpulse-17.0 gtk
=media-libs/libsndfile-1.2.2-r2 -minimal
=media-libs/libsndfile-1.2.2-r2 -alsa -minimal
=app-alternatives/cpio-0 -split-usr
=dev-python/certifi-3021.3.16-r4 -python_targets_python3_10
=dev-python/setuptools-69.1.1 -python_targets_python3_10
=dev-libs/libxmlb-0.3.14 introspection
=dev-python/pygobject-3.46.0 -python_targets_python3_10
=dev-libs/libzip-1.9.2 -gnutls
=media-libs/gst-plugins-bad-1.20.6 gtk
=x11-libs/wxGTK-3.2.2.1-r3 keyring
=dev-python/cython-3.0.9 -python_targets_python3_10
=app-text/ghostscript-gpl-10.02.1 gtk
=media-libs/libsdl2-2.28.5 -jack -pipewire
=media-libs/libsdl2-2.28.5 -jack
=media-libs/libwebp-1.3.2 cpu_flags_x86_sse4_1
=net-libs/libsoup-3.4.4 -samba
=net-libs/libsoup-3.4.4 -samba sysprof
=net-fs/samba-4.18.9 systemd -winbind
=net-fs/samba-4.18.9 -winbind
=net-libs/glib-networking-2.78.0 gnome
=sys-libs/tdb-1.4.8 -python
=sys-libs/tevent-0.14.1 -python
=media-libs/glm-1.0.1 cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_sse3 cpu_flags_x86_sse4_1 cpu_flags_x86_sse4_2 cpu_flags_x86_ssse3
=x11-libs/gtk+-2.24.33-r3 -xinerama
=media-libs/portaudio-19.07.00-r2 -jack
=net-firewall/iptables-1.8.10 -split-usr
=dev-libs/libpcre-8.45-r3 -pcre16
=media-libs/flac-1.4.3 cpu_flags_x86_avx cpu_flags_x86_avx2
=media-libs/flac-1.4.3 cpu_flags_x86_avx cpu_flags_x86_avx2 -ogg
=media-libs/libv4l-1.22.1 -dvb
=media-libs/libfreeaptx-0.1.1-r1 cpu_flags_x86_avx2
=dev-libs/libcdio-2.1.0-r1 -cddb
=media-sound/lame-3.100-r3 frontend -sndfile
=media-plugins/gst-plugins-meta-1.20.6 -dvb -ffmpeg -jack -lame -taglib -theora -v4l
=media-plugins/gst-plugins-meta-1.20.6 -dvb -ffmpeg -jack -lame -taglib
=dev-libs/boost-1.84.0-r3 -python
=dev-libs/boost-1.84.0-r3 -icu -python
=media-libs/rubberband-3.3.0-r1 -ladspa
=net-dns/avahi-0.8-r7 gtk systemd
=media-libs/babl-0.1.106 cpu_flags_x86_avx2 cpu_flags_x86_f16c cpu_flags_x86_sse4_1 -introspection
=media-libs/babl-0.1.106 cpu_flags_x86_avx2 cpu_flags_x86_f16c cpu_flags_x86_sse4_1
=media-libs/gegl-0.4.46 -ffmpeg -raw -v4l
=media-libs/gegl-0.4.46 -ffmpeg introspection -v4l
=media-libs/libmypaint-1.6.1-r2 -gegl introspection
=media-libs/libmypaint-1.6.1-r2 -gegl
=dev-qt/qtwebengine-5.15.12_p20240122 bindist
=dev-qt/qtwebengine-5.15.12_p20240122 bindist -screencast
=media-libs/opencv-4.8.1-r1 cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_f16c cpu_flags_x86_fma3 cpu_flags_x86_popcnt cpu_flags_x86_sse3 cpu_flags_x86_sse4_1 cpu_flags_x86_sse4_2 cpu_flags_x86_ssse3 -ffmpeg gstreamer -ieee1394 -java -v4l video_cards_intel -xine
=media-libs/opencv-4.8.1-r1 cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_f16c cpu_flags_x86_fma3 cpu_flags_x86_popcnt cpu_flags_x86_sse3 cpu_flags_x86_sse4_1 cpu_flags_x86_sse4_2 cpu_flags_x86_ssse3 -ffmpeg -ieee1394 -java -v4l video_cards_intel -xine
=media-gfx/imagemagick-7.1.1.25 -raw
=kde-frameworks/kfilemetadata-5.115.0 -ffmpeg
=media-libs/openexr-3.1.11 cpu_flags_x86_avx
=sci-libs/hdf5-1.14.3-r1 -cxx
=app-arch/snappy-1.1.10-r1 cpu_flags_x86_avx cpu_flags_x86_avx2
=net-libs/libsoup-2.74.3 -samba
=net-libs/libsoup-2.74.3 -samba sysprof
=gui-libs/gtk-4.12.4 -colord cpu_flags_x86_f16c
=gui-libs/gtk-4.12.4 cpu_flags_x86_f16c gstreamer sysprof
=media-gfx/fontforge-20230101 gtk
=kde-plasma/powerdevil-5.27.11 wireless
=net-misc/networkmanager-1.42.6-r2 -gnutls nss
=sys-apps/smartmontools-7.4-r1 systemd
=net-dialup/ppp-2.5.0-r6 gtk
=net-dialup/ppp-2.5.0-r6 gtk systemd
=x11-misc/xdg-user-dirs-0.18 gtk
=x11-base/xwayland-23.2.4 libei systemd
=x11-base/xwayland-23.2.4 systemd
=x11-base/xwayland-23.2.4 libei
=media-sound/fluidsynth-2.3.4-r1 -jack -ladspa -portaudio systemd
=media-sound/fluidsynth-2.3.4-r1 -jack -ladspa -pipewire -portaudio
=media-libs/openal-1.23.1-r1 cpu_flags_x86_sse4_1 -jack -portaudio
=media-libs/openal-1.23.1-r1 cpu_flags_x86_sse4_1 -jack -pipewire -portaudio
=dev-libs/libsodium-1.0.19-r2 cpu_flags_x86_sse4_1
=kde-apps/gwenview-23.08.5 -raw
=kde-apps/gwenview-23.08.5 -activities -raw -semantic-desktop
=kde-apps/okular-23.08.5 -epub
=kde-apps/okular-23.08.5 -epub -qml
=kde-apps/thumbnailers-23.08.5 -raw
=kde-frameworks/kimageformats-5.115.0 -raw
=media-libs/libgphoto2-2.5.30 -gd
=gnome-base/gvfs-1.52.1 -elogind gnome-online-accounts keyring -samba systemd
=gnome-base/gvfs-1.52.1 -elogind -samba systemd
=gnome-base/gvfs-1.52.1 gnome-online-accounts keyring -samba
=dev-libs/xmlsec-1.3.3-r1 -gcrypt -gnutls
=dev-libs/redland-1.0.17-r3 -mysql
=dev-db/mariadb-connector-c-3.2.7 -gnutls
=net-libs/webkit-gtk-2.42.4-r410 keyring
=net-libs/webkit-gtk-2.42.4-r410 keyring systemd
=net-libs/webkit-gtk-2.42.4-r410 systemd
=dev-libs/elfutils-0.190 -static-libs
=virtual/libintl-0-r2 -abi_x86_32
=virtual/libiconv-0-r2 -abi_x86_32
=sys-apps/systemd-utils-254.8 -abi_x86_32 -split-usr
=sys-libs/libxcrypt-4.4.36 -split-usr
=sys-libs/libxcrypt-4.4.36 -abi_x86_32 -split-usr
=dev-lang/python-3.12.2_p1 -bluetooth
=dev-libs/libusb-1.0.26 -split-usr
=kde-apps/kio-extras-23.08.5 -mtp -nfs -samba -taglib
=kde-apps/kio-extras-23.08.5 -activities -mtp -nfs -phonon -samba -taglib
=dev-db/mariadb-10.6.17 bindist -extraengine
=dev-db/mariadb-10.6.17 bindist -extraengine systemd
=net-misc/networkmanager-1.42.6-r2 -elogind -gnutls nss systemd
=net-mail/mailutils-3.15 -mysql -split-usr
NOTE: The --binpkg-respect-use=n option will prevent emerge
from ignoring these binary packages if possible.
Using --binpkg-respect-use=y will silence this warning.
|
My make.conf USE are following:
Code: | USE="bluetooth cxx colord -consolekit -nocxx cddb -doc drm dvb elogind dbus ffmpeg gd gimp gnutls -gnome -gtk ieee1394 jack jack-tmpfs java jumbo-build ladspa mysql networkmanager pam png policykit portaudio qtwebengine raw samba sndfile sse sse2 -systemd taglib theora v4l vst X xinerama" |
|
|
Back to top |
|
|
logrusx Veteran
Joined: 22 Feb 2018 Posts: 1726
|
Posted: Tue Mar 26, 2024 6:36 am Post subject: |
|
|
That means those packages will be compiled because their use flags do not match the flags with which the binary packages were built. You can either continue and build them or adjust the use flags wherever you consider it OK for you and maximize the list of binary packages that will be used.
In the list it's shown what change need to be made, e.g. -abi_x86_32 means you need to turn off the 32bit support for those packages as you can't get it from binary packages. If the case is like mine where those are needed by wine you have no choice but rebuild them.
Furthermore it looks like this is an OpenRC installation and it doesn't make sense for you to enable systemd support to accommodate the packages required to have it for the binary package to be used. However systemd support alone doesn't do much, so it could be a viable option even for OpenRC users who just want to use binary packages. This route should be further explored if someone is interested as it's beyond me.
Best Regards,
Georgi |
|
Back to top |
|
|
e8root Tux's lil' helper
Joined: 09 Feb 2024 Posts: 86
|
Posted: Tue Mar 26, 2024 8:08 am Post subject: |
|
|
My understanding is that there are multiple version of binary packages which have been built by Gentoo binary package build system and each duplicated entry here present possible option for you what changes to make to be able to use binary package. Having to build each package in multiple versions is a much bigger burden than binary packages in most distros. Ideally we would have each permutation of each package for each CPU type but this is not feasible... unless some millionaire Gentoo enthusiast funds such endeavor
Out of interest what is available in regards to systemd vs -systemd I checked each systemd entry and it seems almost all systemd entries have the same option without systemd specific use flags.
Why this entry =sys-apps/systemd-utils-254.8 -abi_x86_32 -split-usr?
It is probably something installed as a dependency for some package which has systemd related use flag - if this is not systemd system then you should probably check your packages and adjust accordingly so such systemd packages are not installed.
ps.
Code: | =dev-libs/libgcrypt-1.10.3-r1 cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_sse4_1 |
Indicates you don't have these cpu flags set. If the PC you use has AVX2 you should probably set CPU flags in make.conf
If not it would explain why you want to use binary packages
Either way most of the changes you would need to make seem inconsequential. If they are then build from sources. Most of these packages are quite smll and should not take too long to build.
And lastly - until we can drop reliance on abi_x86_32 (which seems to be something that currently mostly Steam and to smaller degree Wine is holding us from doing) I hope Gentoo maintainers will consider building abi_x86_32 packages just for Wine/Steam. Also if you do not use Steam please consider using wow64. It works fairly well with Wine 9.x if you do not need 16-bit application support. _________________ Unix Wars - Episode V: AT&T Strikes Back |
|
Back to top |
|
|
flexibeast Guru
Joined: 04 Apr 2022 Posts: 325 Location: Naarm/Melbourne, Australia
|
Posted: Tue Mar 26, 2024 8:25 am Post subject: |
|
|
e8root wrote: | Ideally we would have each permutation of each package for each CPU type but this is not feasible... unless some millionaire Gentoo enthusiast funds such endeavor |
Even that wouldn't be sufficient, because, well, take Firefox as an example. It has 129 USE flags, meaning there are 2^129 ≅ 6.8 x 10^38, i.e. 680,000,000,000,000,000,000,000,000,000,000,000,000 different versions that would need to be built and made available for download. Even if we remove all the localisation flags, there would still be 2^30 = 1,073,741,824 versions that would need to be built and made available for download. And that's for just one version of one package for one architecture. |
|
Back to top |
|
|
logrusx Veteran
Joined: 22 Feb 2018 Posts: 1726
|
Posted: Tue Mar 26, 2024 9:34 am Post subject: |
|
|
e8root wrote: |
Why this entry =sys-apps/systemd-utils-254.8 -abi_x86_32 -split-usr?
It is probably something installed as a dependency for some package which has systemd related use flag - if this is not systemd system then you should probably check your packages and adjust accordingly so such systemd packages are not installed. |
This is not a systemd dependency. Quite the contrary, systemd contains it, so it doesn't need to depend on it. As the description of the package says, this is a split of systemd utilities to be available for use in openrc installations.
Best Regards,
Georgi |
|
Back to top |
|
|
hunky l33t
Joined: 19 Nov 2003 Posts: 912 Location: Alaska
|
Posted: Tue Mar 26, 2024 4:08 pm Post subject: |
|
|
e8root wrote: |
Why this entry =sys-apps/systemd-utils-254.8 -abi_x86_32 -split-usr?
It is probably something installed as a dependency for some package which has systemd related use flag - if this is not systemd system then you should probably check your packages and adjust accordingly so such systemd packages are not installed.
ps.
Code: | =dev-libs/libgcrypt-1.10.3-r1 cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_sse4_1 |
Indicates you don't have these cpu flags set. If the PC you use has AVX2 you should probably set CPU flags in make.conf
If not it would explain why you want to use binary packages
And lastly - until we can drop reliance on abi_x86_32 (which seems to be something that currently mostly Steam and to smaller degree Wine is holding us from doing) I hope Gentoo maintainers will consider building abi_x86_32 packages just for Wine/Steam. Also if you do not use Steam please consider using wow64. It works fairly well with Wine 9.x if you do not need 16-bit application support. |
Systemd: Updating along my merry way, over time I've seen systemd packages creeping into my system despite my -systemd USE flag. I figured something I used pulled them in and figured it was the price of doing business these days. I'm not dead set against it, just didn't want to have to learn a new system at my age, plus some people undoubtedly put a bug in my ear against systemd despite me not knowing that much about it. They seemed to have reasoned biases.
There are several entries in my package.use that have the abi_x86_32 USE set. Like rust-bin, glib, icu, etc.. lots. I could start trying to remove some and see how they respond. At this point I don't have Steam or Wine installed.
First I've heard of AVX2. I have a AMD Ryzen 7 5700G CPU.. so not sure about that one.
Lastly.. I hadn't intended on moving toward bin packages.. didn't mind compiling except for some of the larger, slower packages like rust, or those that pulled in qtwebengine otherwise. I'll have to read up some more.. is the Gentoo intention on moving towards binary or remaining a source distro with binary options? Is the command emerge --ask --emptytree --getbinpkg @world rebuilding my world into binary packages as it seems it would and is that needed.. or can I drop the --getbinpkg and just rebuild world for the new profile.. my confusion on display. I'll do a bit more research.
Thanks a bunch for the detailed reply! |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21894
|
Posted: Tue Mar 26, 2024 4:22 pm Post subject: |
|
|
To get the full benefit of the profile changes, you need all your native programs rebuilt with the new toolchain settings. emerge --emptytree @world ensures that happens. Using emerge --emptytree --getbinpkg @world is offered as an alternative for people who want the new settings, but do not want to spend time rebuilding @world. That command will reinstall everything, and use binary packages built by the Gentoo project wherever it can. Going forward, you can do your regular system updates without --getbinpkg, and the system will slowly adjust back to being built exactly as you like it. Alternatively, if you have the CPU cycles to spare and want maximal control, you can omit --getbinpkg and do all the rebuilds locally.
You also have the option of not rebuilding everything right now, and letting that get picked up over time. However, absent specific encouragement from the Gentoo developers to do that, I cannot recommend it, as I have no insight into whether this will make your system too different from baseline for us to help you. I am not aware of anything that will break, but we do know that you will not get the benefits of the improved toolchain until you install binaries built with it, either built for you (--getbinpkg) or built locally (without --getbinpkg). |
|
Back to top |
|
|
hunky l33t
Joined: 19 Nov 2003 Posts: 912 Location: Alaska
|
Posted: Tue Mar 26, 2024 4:24 pm Post subject: |
|
|
logrusx wrote: | That means those packages will be compiled because their use flags do not match the flags with which the binary packages were built. You can either continue and build them or adjust the use flags wherever you consider it OK for you and maximize the list of binary packages that will be used.
In the list it's shown what change need to be made, e.g. -abi_x86_32 means you need to turn off the 32bit support for those packages as you can't get it from binary packages. If the case is like mine where those are needed by wine you have no choice but rebuild them.
Furthermore it looks like this is an OpenRC installation and it doesn't make sense for you to enable systemd support to accommodate the packages required to have it for the binary package to be used. However systemd support alone doesn't do much, so it could be a viable option even for OpenRC users who just want to use binary packages. This route should be further explored if someone is interested as it's beyond me.
Best Regards,
Georgi |
Yes.. OpenRC with some bias against systemd, whether informed or not. Don't want to engage that argument. Something I have pulled in some systemd packages.. I can live with that as long as I can keep my OpenRC system intact without too much systemd.
As my reply to e8root regarding abi_x86_32.. several packages in my package.use file have that flag.. at some point an upgrade must have required it because I wouldn't have put that flag in there without something wanting it. My PC is a recent build (a year or so old) with a fairly modern AMD Ryzen CPU.
I hadn't intended on moving to a binary system.. just the packages that pulled in qtwebengine or were maybe large and slow to compile.
I really appreciate your response - thanks much! regards, JD |
|
Back to top |
|
|
logrusx Veteran
Joined: 22 Feb 2018 Posts: 1726
|
Posted: Tue Mar 26, 2024 4:29 pm Post subject: |
|
|
hunky wrote: | is the Gentoo intention on moving towards binary or remaining a source distro with binary options? |
It's not moving anywhere. Those are features that have been here for a long time now. It's just that now you can use binary packages produced by somebody else and Gentoo now provides those. They are even signed.
hunky wrote: | Is the command emerge --ask --emptytree --getbinpkg @world rebuilding my world into binary packages as it seems it would and is that needed.. or can I drop the --getbinpkg and just rebuild world for the new profile.. |
You can drop the --getbinpkg. That would be just a longer (time and energy wise) route. Although using binary packages takes several hours too on my 5800H.
BTW I totally understand not wanting to learn a new system. I'm already starting to find it hard.
Best Regards,
Georgi |
|
Back to top |
|
|
hunky l33t
Joined: 19 Nov 2003 Posts: 912 Location: Alaska
|
Posted: Tue Mar 26, 2024 4:31 pm Post subject: |
|
|
Hu wrote: | To get the full benefit of the profile changes, you need all your native programs rebuilt with the new toolchain settings. emerge --emptytree @world ensures that happens. Using emerge --emptytree --getbinpkg @world is offered as an alternative for people who want the new settings, but do not want to spend time rebuilding @world. That command will reinstall everything, and use binary packages built by the Gentoo project wherever it can. Going forward, you can do your regular system updates without --getbinpkg, and the system will slowly adjust back to being built exactly as you like it. Alternatively, if you have the CPU cycles to spare and want maximal control, you can omit --getbinpkg and do all the rebuilds locally.
You also have the option of not rebuilding everything right now, and letting that get picked up over time. However, absent specific encouragement from the Gentoo developers to do that, I cannot recommend it, as I have no insight into whether this will make your system too different from baseline for us to help you. I am not aware of anything that will break, but we do know that you will not get the benefits of the improved toolchain until you install binaries built with it, either built for you (--getbinpkg) or built locally (without --getbinpkg). |
Excellent advice and understandable. Thanks Hu! You've helped me a lot in the past as well. Based on this, I will go with the --emptytree. My usual upgrade command is emerge -atuv -DU --keep-going @world, for better or worse.. and after the world rebuild will continue with that. I may add the --newuse if I start trying to reduce the abi_x86_32 in my package.use file, but that is another topic. |
|
Back to top |
|
|
|
|
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
|
|