libdrm keeps wanting extra video cards? [SOLVED]

[Illiander]

I'm doing a clean install on new hardware, and I'm at the point of installing desktop applications, some of which need gtk+.

Which needs libdrm.

Which keeps wanting USE flags for a bunch of graphics cards that I don't have. Sometimes it asks for what looks like every graphics card USE flag.

How do I make it not do that?

Or is it safe to give libdrm the extra flags, and it won't break my nvidia-drivers? (I'm running proprietary nvidia)

[grknight]

Please show the entire output you are questioning.

Also, what does grep -ri video_cards /etc/portage/ output?

[Illiander]

Emerge output:

Code: Select all

# emerge @preserved-rebuild
Calculating dependencies... done!
Dependency resolution took 2.54 s.

[ebuild   R    ] x11-libs/libdrm-2.4.115  VIDEO_CARDS="amdgpu* nouveau* radeon*" 
[ebuild   R    ] x11-drivers/xf86-video-amdgpu-23.0.0 
[ebuild   R    ] x11-drivers/xf86-video-ati-22.0.0 
[ebuild   R    ] x11-drivers/xf86-video-nouveau-1.0.17 

The following USE changes are necessary to proceed:
 (see "package.use" in the portage(5) man page for more details)
# required by x11-drivers/xf86-video-ati-22.0.0::gentoo
# required by @preserved-rebuild (argument)
>=x11-libs/libdrm-2.4.115 video_cards_nouveau video_cards_radeon video_cards_amdgpu

Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.

grep output:

Code: Select all

# grep -ri video_cards /etc/portage/
/etc/portage/package.use/nvidia:media-libs/mesa -video_cards_amdgpu -video_cards_intel -video_cards_nouveau -video_cards_radeon
/etc/portage/make.conf:USE="-kde -qt4 -mono -systemd -gnome -video_cards_amdgpu -video_cards_intel -video_cards_nouveau -video_cards_radeon aalib acpi apache2 atm bash-completion bidi caps cddb cdinstall cgi cjk css cups curl cvs cxx dga djvu dv dvb dvd dist-kernel dvdr emacs encode exif expat fbcon ffmpeg fltk freetds freewnn ftp gd geoip gimp git gsm gstreamer hardened hddtemp idn ieee1394 imagemagick imap ipv6 java javascript joystick jpeg jpeg2k kerberos latex libwww lirc lmsensors lua lz4 mad magic matroska mikimod mmap mng mp3 mp4 mpeg mtp musepack musicbrainz mysql mysqli ncurses nntp nocd nsplugin offensive openexr php portaudio postscript pulseaudio python qmail-spp quicktime raw readline rss samba sasl scanner session smp sockets socks5 sound source sox spell ssl subversion svga tcl theora unicode v4l vcd videos vulkan wavpack wmf x264 xine xinerama amp xscreensaver zeroconf zsh-completion"
/etc/portage/make.conf:VIDEO_CARDS="nvidia"

I probably don't need all those use flags explicitly turned on since I'm on a desktop profile if I'm being honest. Holdovers from previous systems.

[grknight]

You should complete a full update, e.g. emerge -avuDU @world, followed up by a depclean, emerge -ac, before trying to target @preserved-rebuild.

This will likely remove the need for the changes and may omit the need for @preserved-rebuild.

[Illiander]

That sorted it, thanks.

Any ideas why it started in the first place?

[grknight]

Any ideas why it started in the first place?

Just order of operations. @preserved-rebuild should be last as it can hold on to libraries which are attached to packages scheduled to be removed. Doing a depclean (aka -c) of the system first, often removes messages for @preserved-rebuild in many cases.

If such calls for @preserved-rebuild remain after a --depclean, then it is worth running.