Summary: | Upgrading sys-devel/gcc and x11-drivers/nvidia-drivers in the same run breaks with kernel's gcc plugins | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | onkobu |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | ionen |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
onkobu
2021-07-27 09:27:14 UTC
>Either build errors out during config or upgrade of gcc during same run does not eselect it.
gcc-10.2 -> 10.3 is not eselect, 10 share the same slot so 10.3 replaces 10.2
That sounds like CANTFIX material.
it's a known "feature" of gcc-plugins in kernel. if you updated compiler, you have to recompile kernel before external drivers can be built with plugins enabled with new compiler. we can't really fix it. just keep an eye on updates and emerge drivers after kernel is rebuilt with new compiler. (In reply to Ionen Wolkens from comment #1) > >Either build errors out during config or upgrade of gcc during same run does not eselect it. > > gcc-10.2 -> 10.3 is not eselect, 10 share the same slot so 10.3 replaces 10.2 > > That sounds like CANTFIX material. $> eselect gcc list [1] armv6j-unknown-linux-gnueabihf-10.2.0 [2] armv6j-unknown-linux-gnueabihf-10.3.0 * [3] armv7a-unknown-linux-gnueabihf-10.2.0 [4] armv7a-unknown-linux-gnueabihf-10.3.0 * [5] x86_64-pc-linux-gnu-10.2.0 [6] x86_64-pc-linux-gnu-10.3.0 * They don't share the same slot, at least not on this particular machine. But I'm fine with the reply. Since I'm not a gcc expert could an ebuild contain a check for this situation? The ebuild would fail then or even the pre-conditions of emerge run? Added some lines to the Wiki: https://wiki.gentoo.org/wiki/NVIDIA/nvidia-drivers#Kernel_GCC_Plugins |