From: Nathan Chancellor <nathan@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
Conor Dooley <conor@kernel.org>,
Conor Dooley <Conor.Dooley@microchip.com>
Subject: Re: Prebuilt LLVM 18.1.0-rc2 uploaded
Date: Tue, 27 Feb 2024 14:56:05 -0700 [thread overview]
Message-ID: <20240227215605.GA1422986@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CANiq72mmDquTeoEVErwXH7bVhP0+UifCrK0n=-HD97noWLqryA@mail.gmail.com>
On Tue, Feb 27, 2024 at 05:51:04PM +0100, Miguel Ojeda wrote:
> On Tue, Feb 27, 2024 at 4:37 PM Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > How far back would you like it added? I don't necessarily mind
> > rebuilding older releases but certain entities may notice the checksums
> > change.
> >
> > https://gitlab.com/Linaro/tuxmake/-/merge_requests/364
> >
> > Not the end of the world though.
>
> I think a reasonable set would be those versions matching the LLVM
> that Rust bundles (for `rustc` versions we have since 6.1 LTS). That
> is: 15, 16 and 17.
>
> Conveniently, LLVM 15 also matches the minimum external LLVM supported
> by `rustc` in 6.6 LTS.
>
> If those are too much, LLVM 17 would already cover what 6.6 LTS' Rust bundles.
15 through 17 is a reasonable rebuild request, I've added it to the
queue along with 18.1.0-rc4, which was just released. I'll message you
when I have them uploaded.
Cheers,
Nathan
next prev parent reply other threads:[~2024-02-27 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 0:28 Nathan Chancellor
2024-02-10 16:36 ` Miguel Ojeda
2024-02-12 23:48 ` Nathan Chancellor
2024-02-13 2:53 ` Nathan Chancellor
2024-02-13 20:37 ` Miguel Ojeda
2024-02-27 12:32 ` Miguel Ojeda
2024-02-27 15:37 ` Nathan Chancellor
2024-02-27 16:51 ` Miguel Ojeda
2024-02-27 21:56 ` Nathan Chancellor [this message]
2024-02-28 18:43 ` Nathan Chancellor
2024-02-29 13:39 ` Miguel Ojeda
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=20240227215605.GA1422986@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=Conor.Dooley@microchip.com \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
/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
all inboxes | Powered by JetHome®