From: Zheng Junjie <zhengjunjie@iscas.ac.cn>
To: Michael Ford <fanquake@gmail.com>
Cc: 71746-done@debbugs.gnu.org
Subject: bug#71746: [PATCH] gnu: LLVM, Clang, libomp, lld: Update to 18.1.8.
Date: Thu, 27 Jun 2024 21:17:16 +0800 [thread overview]
Message-ID: <87cyo2o78j.fsf@iscas.ac.cn> (raw)
In-Reply-To: <CAFyhPjVOT8gq3QJ6rXpaEArQuZ8FC0coT4qC_G8mM-gtniJ_Jw@mail.gmail.com> (Michael Ford's message of "Mon, 24 Jun 2024 11:59:01 +0100")
[-- Attachment #1: Type: text/plain, Size: 2232 bytes --]
Michael Ford <fanquake@gmail.com> writes:
> From a9a9dc58c0c66cd8245265a3b69beb43c6953a8c Mon Sep 17 00:00:00 2001
> From: fanquake <fanquake@gmail.com>
> Date: Mon, 24 Jun 2024 10:09:35 +0100
> Subject: [PATCH] gnu: LLVM, Clang, libomp, lld: Update to 18.1.8.
>
> * gnu/packages/llvm.scm (llvm-18, clang-18, libomp-18, lld-18): Update to
> 18.1.8.
> ---
> gnu/packages/llvm.scm | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/gnu/packages/llvm.scm b/gnu/packages/llvm.scm
> index 971f5b2e25..eceda150b8 100644
> --- a/gnu/packages/llvm.scm
> +++ b/gnu/packages/llvm.scm
> @@ -550,7 +550,7 @@ (define %llvm-monorepo-hashes
> ("15.0.7" . "12sggw15sxq1krh1mfk3c1f07h895jlxbcifpwk3pznh4m1rjfy2")
> ("16.0.6" . "0jxmapg7shwkl88m4mqgfjv4ziqdmnppxhjz6vz51ycp2x4nmjky")
> ("17.0.6" . "1a7rq3rgw5vxm8y39fyzr4kv7w97lli4a0c1qrkchwk8p0n07hgh")
> - ("18.1.7" . "1c77pcqsfgvnxa3zq2i7giz86d6cdzl1scphi2dmcq3n73bzy4m8")))
> + ("18.1.8" . "1l9wm0g9jrpdf309kxjx7xrzf13h81kz8bbp0md14nrz38qll9la")))
>
> (define %llvm-patches
> '(("14.0.6" . ("clang-14.0-libc-search-path.patch"))
> @@ -558,7 +558,7 @@ (define %llvm-patches
> ("16.0.6" . ("clang-16.0-libc-search-path.patch"))
> ("17.0.6" . ("clang-17.0-libc-search-path.patch"
> "clang-17.0-link-dsymutil-latomic.patch"))
> - ("18.1.7" . ("clang-18.0-libc-search-path.patch"
> + ("18.1.8" . ("clang-18.0-libc-search-path.patch"
> "clang-17.0-link-dsymutil-latomic.patch"))))
>
> (define (llvm-monorepo version)
> @@ -1454,7 +1454,7 @@ (define-public clang-toolchain-17
> (define-public llvm-18
> (package
> (inherit llvm-15)
> - (version "18.1.7")
> + (version "18.1.8")
> (source (llvm-monorepo version))))
>
> (define-public clang-runtime-18
> @@ -1470,7 +1470,7 @@ (define-public clang-18
> (package-version llvm-18)))
> (sha256
> (base32
> - "0f1g9mlz4jmrws9sd81j1b8q5i2frvln6gp5vrvbdlzks5mlpj95")))))
> + "1wd7y1a0db4y51swlq6dmm9hrv8pvmv158yi9f10dlayv7y7g275")))))
>
> (define-public libomp-18
> (package
push, see https://git.savannah.gnu.org/cgit/guix.git/commit/?id=c99b1e2fc6747e589326a6d882332e6247e1b553
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2024-06-27 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 10:59 [bug#71746] [PATCH] gnu: LLVM, Clang, libomp, lld: Update to 18.1.8 Michael Ford
2024-06-27 13:17 ` Zheng Junjie [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=87cyo2o78j.fsf@iscas.ac.cn \
--to=zhengjunjie@iscas.ac.cn \
--cc=71746-done@debbugs.gnu.org \
--cc=fanquake@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.
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).