On Sunday, January 1, 2023 11:38:36 AM CET Łukasz Kalamłacki wrote: > > On 1.01.2023 11:20, Greg KH wrote: > > On Sun, Jan 01, 2023 at 10:12:12AM +0000, Łukasz Kalamłacki wrote: > >> Allright, my kernel config is available here: > >> https://kalamlacki.eu/KERNELS/kconfig-6.1 > >> > >> Compilation on 11th gen i5 core cpu using command: > >> > >> make -j 9 bindeb-pkg > > As we have both stated, we are not the people to be discussing this > > with as the kernel source is not the problem at all, so there's nothing > > we can do here, sorry. > > > > Have a good new year! > > > > greg k-h > > I am aware Greg that this is not kernel release issue and rather gcc but > it occurs during kernel compilation and many people can have this issue > too and that is why I am discussing about it here. > > Willy: Debian stable has gcc in version 10.2.1 as states my buildinfo > from compilation of kernel 6.1.1 as it can be checked here: > https://kalamlacki.eu/KERNELS/BUSTER/linux-upstream_6.1.1-1_amd64.buildinfo. > > I had the same issue with you as I am using Debian 11 (bullseye) and followed Willy's suggestion to use the toolchains available on https://mirrors.edge.kernel.org/pub/tools/crosstool/, that solved my problem for compiling 6.0.16 version as well. 6.0.X kernel versions are already available via backports, so I think the fix to GCC version, that bullseye utilizes, will come to bullseye quite soon as the kernel package maintainers will see the issue when they will try to release 6.0.16 version to backports. This issue was a strong reminder for me to switch back to the toolchains for compiling the kernel. I do acknowledge that it is quite convenient for users to just use the GCC that is available from the distribution but using the aforementioned toolchains ensures a smooth experience with compiling the kernel. My 2 cents, Pavlos
