From: Hilton Chain via Guix-patches via <guix-patches@gnu.org>
To: Michael Ford <fanquake@gmail.com>
Cc: 67625-done@debbugs.gnu.org, Greg Hogan <code@greghogan.com>
Subject: bug#67625: Subject: [PATCH] gnu: LLVM, Clang, libomp, lld: Update to 17.0.6.
Date: Sun, 10 Dec 2023 12:18:03 +0800 [thread overview]
Message-ID: <87o7eyk7wk.wl-hako@ultrarare.space> (raw)
In-Reply-To: <CAFyhPjV2KD6c_DU+ku-k_3YfCEa4pHJCRdrkxHHUB_0V0w8=2Q@mail.gmail.com>
Hi Michael,
On Tue, 05 Dec 2023 18:49:29 +0800,
Michael Ford wrote:
>
> It should. Forgot about this, and then only built LLVM, not a full
> Clang toolchain.
> Have done that now. Updated patch below:
>
> From 10fa8bf8d5eeebdb4fcf0142617af2f54e43beb5 Mon Sep 17 00:00:00 2001
> From: fanquake <fanquake@gmail.com>
> Date: Mon, 4 Dec 2023 14:07:15 +0000
> Subject: [PATCH] gnu: LLVM, Clang, libomp, lld: Update to 17.0.6.
>
> * gnu/packages/llvm.scm (llvm-17, clang-17, libomp-17, lld-17):
> Update to 17.0.6.
> ---
> gnu/packages/llvm.scm | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Applied as 2e11caff39d502775d7c652972a441f5da3d9eec, thank you!
> On Mon, 4 Dec 2023 at 18:41, Greg Hogan <code@greghogan.com> wrote:
> >
> > On Mon, Dec 4, 2023 at 11:21 AM Michael Ford <fanquake@gmail.com> wrote:
> > >
> > > From 52ca0b1749fcb845f8015a33364beae489c08bf4 Mon Sep 17 00:00:00 2001
> > > From: fanquake <fanquake@gmail.com>
> > > Date: Mon, 4 Dec 2023 14:07:15 +0000
> > > Subject: [PATCH] gnu: LLVM, Clang, libomp, lld: Update to 17.0.6.
> > >
> > > * gnu/packages/llvm.scm (llvm-17, clang-17, libomp-17, lld-17):
> > > Update to 17.0.6.
> > > ---
> > > gnu/packages/llvm.scm | 6 +++---
> > > 1 file changed, 3 insertions(+), 3 deletions(-)
[...]
> >
> > Should this also update the clang-tools-extra hash?
And thanks to Greg for the review!
prev parent reply other threads:[~2023-12-10 5:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 16:20 [bug#67625] Subject: [PATCH] gnu: LLVM, Clang, libomp, lld: Update to 17.0.6 Michael Ford
2023-12-04 18:41 ` Greg Hogan
2023-12-05 10:49 ` Michael Ford
2023-12-10 4:18 ` Hilton Chain via Guix-patches via [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7eyk7wk.wl-hako@ultrarare.space \
--to=guix-patches@gnu.org \
--cc=67625-done@debbugs.gnu.org \
--cc=code@greghogan.com \
--cc=fanquake@gmail.com \
--cc=hako@ultrarare.space \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).