All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	stable <stable@vger.kernel.org>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-x86_64@vger.kernel.org
Subject: Re: LTS kernel Linux 4.14.290 unable to boot with edk2-ovmf (x86_64 UEFI runtime)
Date: Mon, 22 Aug 2022 10:30:44 +0200	[thread overview]
Message-ID: <20220822083044.GC17080@1wt.eu> (raw)
In-Reply-To: <4c42af33-dc05-315a-87d9-be0747a74df4@gmx.com>

On Mon, Aug 22, 2022 at 04:19:49PM +0800, Qu Wenruo wrote:
> > Regardless, if you need an older compiler, just use these ones:
> > 
> >     https://mirrors.edge.kernel.org/pub/tools/crosstool/
> > 
> > They go back to 4.9.4 for x86, you'll surely find the right one for your
> > usage. I've long used 4.7.4 for kernels up to 4.9 and 6.5 for 4.19 and
> > above, so something within that area will surely match your needs.
> 
> BTW, it would be way more awesome if the page can provide some hint on
> the initial release date of the compilers.
> 
> It would help a lot of choose the toolchain then.

It wouldn't help, if you look closely, you'll notice that in the "other
releases" section you have the most recent version of each of them. That
does not preclude the existence of the branch earlier. For example gcc-9
was released in 2019 and 9.5 was emitted 3 years later. That's quite an
amplitude that doesn't help.

Willy

  reply	other threads:[~2022-08-22  8:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22  1:15 LTS kernel Linux 4.14.290 unable to boot with edk2-ovmf (x86_64 UEFI runtime) Qu Wenruo
2022-08-22  6:25 ` Greg KH
2022-08-22  7:24   ` Qu Wenruo
2022-08-22  7:33     ` Greg KH
2022-08-22  7:49       ` Qu Wenruo
2022-08-22  7:58         ` Greg KH
2022-08-22  8:13           ` Qu Wenruo
2022-08-22  9:00             ` Greg KH
2022-08-22 11:43               ` Qu Wenruo
2022-08-22 11:58                 ` Willy Tarreau
2022-08-22 12:06                   ` Qu Wenruo
2022-08-22  8:04         ` Willy Tarreau
2022-08-22  8:19           ` Qu Wenruo
2022-08-22  8:30             ` Willy Tarreau [this message]
2022-08-22 11:07               ` Qu Wenruo
2022-08-22 11:42                 ` Greg KH
2022-08-22 11:53                 ` Willy Tarreau
2022-08-22 11:59                   ` Qu Wenruo

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=20220822083044.GC17080@1wt.eu \
    --to=w@1wt.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-x86_64@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.