From: Greg Hogan <code@greghogan.com>
To: 56666@debbugs.gnu.org
Cc: Greg Hogan <code@greghogan.com>
Subject: [bug#56666] [PATCH 06/17] gnu: clang-toolchain-11: Use libomp-11.
Date: Wed, 20 Jul 2022 15:09:00 +0000 [thread overview]
Message-ID: <8c93b3c9b63210dedeb3c454c9c3e288e7b9148a.1658327898.git.code@greghogan.com> (raw)
In-Reply-To: <cover.1658327897.git.code@greghogan.com>
* gnu/packages/llvm.scm (clang-toolchain-11): Switch dependency from the
default libomp-13 to libomp-11.
---
gnu/packages/llvm.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnu/packages/llvm.scm b/gnu/packages/llvm.scm
index 07c86b6354..07622a63cf 100644
--- a/gnu/packages/llvm.scm
+++ b/gnu/packages/llvm.scm
@@ -926,7 +926,7 @@ (define-public libomp-11
(replace "llvm" llvm-11)))))
(define-public clang-toolchain-11
- (make-clang-toolchain clang-11))
+ (make-clang-toolchain clang-11 libomp-11))
(define-public llvm-10
(package
--
2.37.0
next prev parent reply other threads:[~2022-07-20 15:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 14:49 [bug#56666] [PATCH 00/17] Add libomp per clang-toolchain Greg Hogan
2022-07-20 15:08 ` [bug#56666] [PATCH 01/17] gnu: libomp-14: Reference llvm-14 version string Greg Hogan
2022-07-20 15:08 ` [bug#56666] [PATCH 02/17] gnu: libomp-13: Reference llvm-13 " Greg Hogan
2022-07-20 15:08 ` [bug#56666] [PATCH 03/17] gnu: Add libomp-12 Greg Hogan
2022-07-20 15:08 ` [bug#56666] [PATCH 04/17] gnu: clang-toolchain-12: Use libomp-12 Greg Hogan
2022-07-20 15:08 ` [bug#56666] [PATCH 05/17] gnu: Add libomp-11 Greg Hogan
2022-07-20 15:09 ` Greg Hogan [this message]
2022-07-20 15:09 ` [bug#56666] [PATCH 07/17] gnu: Add libomp-10 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 08/17] gnu: clang-toolchain-10: Use libomp-10 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 09/17] gnu: Add libomp-9 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 10/17] gnu: clang-toolchain-9: Use libomp-9 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 11/17] gnu: Add libomp-8 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 12/17] gnu: clang-toolchain-8: Use libomp-8 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 13/17] gnu: Add libomp-7 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 14/17] gnu: clang-toolchain-7: Use libomp-7 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 15/17] gnu: Add libomp-6 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 16/17] gnu: clang-toolchain-6: Use libomp-6 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 17/17] gnu: make-clang-toolchain: Require explicit libomp Greg Hogan
2022-08-04 9:39 ` bug#56666: [PATCH 00/17] Add libomp per clang-toolchain Ludovic Courtès
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=8c93b3c9b63210dedeb3c454c9c3e288e7b9148a.1658327898.git.code@greghogan.com \
--to=code@greghogan.com \
--cc=56666@debbugs.gnu.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.
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).