From: Pavlos Parissis <pavlos.parissis@gmail.com>
To: "Greg KH" <gregkh@linuxfoundation.org>,
"Łukasz Kalamłacki" <lukasz@pm.kalamlacki.eu>
Cc: Willy Tarreau <w@1wt.eu>, stable@vger.kernel.org
Subject: Re: Cannot compile 6.1.2 kernel release
Date: Mon, 02 Jan 2023 01:13:09 +0100 [thread overview]
Message-ID: <2519789.f74NuczQXU@poseidonas> (raw)
In-Reply-To: <4c7bdbc1-0337-9cf2-8957-94a5f702a49c@pm.kalamlacki.eu>
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
next prev parent reply other threads:[~2023-01-02 0:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 16:58 Cannot compile 6.1.2 kernel release Łukasz Kalamłacki
2023-01-01 6:53 ` Willy Tarreau
2023-01-01 8:14 ` Łukasz Kalamłacki
2023-01-01 8:47 ` Greg KH
2023-01-01 9:01 ` Łukasz Kalamłacki
2023-01-01 10:05 ` Willy Tarreau
2023-01-01 10:12 ` Łukasz Kalamłacki
2023-01-01 10:20 ` Greg KH
2023-01-01 10:38 ` Łukasz Kalamłacki
2023-01-02 0:13 ` Pavlos Parissis [this message]
2023-01-02 3:35 ` Bagas Sanjaya
2023-01-02 3:55 ` Willy Tarreau
2023-01-03 16:32 ` Łukasz Kalamłacki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2519789.f74NuczQXU@poseidonas \
--to=pavlos.parissis@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lukasz@pm.kalamlacki.eu \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox