Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Ł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: Sun, 1 Jan 2023 09:47:31 +0100	[thread overview]
Message-ID: <Y7FIo0Eup6TKswTA@kroah.com> (raw)
In-Reply-To: <d3f0d0a5-a15f-9735-5f12-b1c00a474531@pm.kalamlacki.eu>

On Sun, Jan 01, 2023 at 08:14:12AM +0000, Łukasz Kalamłacki wrote:
> 
> On 1.01.2023 07:53, Willy Tarreau wrote:
> > On Sat, Dec 31, 2022 at 04:58:51PM +0000, Lukasz Kalamlacki wrote:
> >> Hey,
> >>
> >>
> >> Do you have an issue compiling 6.1.2 linux kernel?
> >>
> >> I cannot compile it.
> > For me it compiles and boots. You'll need to share your config and error
> > report if you want to get some help.
> >
> > Willy
> 
> I was trying to compile on Debian Bullseye where default gcc is version
> 10, when I upgraded gcc to version 12 from sid repo i Was able to
> compile too. On stable Debian without addition during compile
> "segmentation fault" occurs at the compilation of cx8-i2c.c file. You
> can try on kvm or virtualbox this compilation.

Sounds like a gcc bug you should be notifying the gcc developers about.

good luck!

greg k-h

  reply	other threads:[~2023-01-01  8:47 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 [this message]
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
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=Y7FIo0Eup6TKswTA@kroah.com \
    --to=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