[packages/kernel] - don't need to require gcc at rpm release level, same version is just fine

[Jan Palus]

On 11.01.2026 11:01, baggins wrote:
> commit 8f16671dc9f4ff5da9bfbb47282c8c22765b689f
> Author: Jan Rękorajski <baggins at pld-linux.org>
> Date:   Sun Jan 11 12:00:27 2026 +0100
> 
>     - don't need to require gcc at rpm release level, same version is just fine

Depends on definition of "fine". gcc with different release but exactly
the same source is indeed fine, but update branch diff between releases
(always modifies DATESTAMP) and it's no longer fine -- kernel module
build will fail on gcc plugin version version compatibility check. I'd
prefer myself to have guarantee kernel and gcc match.

> 
>  kernel.spec | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> ---
> diff --git a/kernel.spec b/kernel.spec
> index 2a2bacb0..d4877357 100644
> --- a/kernel.spec
> +++ b/kernel.spec
> @@ -464,7 +464,7 @@ Summary(pl.UTF-8):	Pliki służące do budowania modułów jądra
>  Group:		Development/Building
>  Requires:	%{name}-headers = %{epoch}:%{version}-%{release}
>  Requires:	elfutils-devel
> -%requires_releq	gcc
> +%requires_eq	gcc
>  Requires:	make
>  Conflicts:	rpmbuild(macros) < 2.019
>  AutoReqProv:	no
> ================================================================
> 
> ---- gitweb:
> 
> http://git.pld-linux.org/gitweb.cgi/packages/kernel.git/commitdiff/8f16671dc9f4ff5da9bfbb47282c8c22765b689f
> 
> _______________________________________________
> pld-cvs-commit mailing list
> pld-cvs-commit at lists.pld-linux.org
> https://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit