From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 59237@debbugs.gnu.org
Subject: [bug#59237] [PATCH 0/3] Add LLVM/Clang 15.0.4.
Date: Tue, 15 Nov 2022 11:33:22 +0100 [thread overview]
Message-ID: <8735ako6bx.fsf_-_@gnu.org> (raw)
In-Reply-To: <20221113050200.27277-3-maxim.cournoyer@gmail.com> (Maxim Cournoyer's message of "Sun, 13 Nov 2022 00:02:00 -0500")
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> * gnu/packages/llvm.scm (clang-from-llvm*): New helper.
> (clang-15): New variable.
[...]
> +;;; TODO: Integrate into original on core-updates, perhaps with an extra
> +;;; option such as #:build-shared-libs? documented as a legacy feature.
> +(define* (clang-from-llvm* llvm clang-runtime
> + #:optional hash
> + #:key (patches '()) tools-extra
> + (properties
> + (append `((release-monitoring-url
> + . ,%llvm-release-monitoring-url))
> + (clang-properties (package-version llvm)))))
[...]
> + #~(modify-phases #$phases
> + ;; Like the original, sans BUILD_SHARED_LIBS patching.
> + #$@(if tools-extra
How about making it an option of ‘clang-from-llvm’ then, like suggested
above?
In ‘clang-from-llvm’, we’d have:
`((add-after 'unpack 'add-tools-extra
(lambda* …
,@(if tools-need-build-shared-libs-patch?
`((substitute* …))
'()
#t))))
That’d factorize things while avoiding a full rebuild.
Ludo’.
next prev parent reply other threads:[~2022-11-15 10:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 4:53 [bug#59237] [PATCH 0/3] Add LLVM/Clang 15.0.4 Maxim Cournoyer
2022-11-13 5:01 ` [bug#59237] [PATCH 1/3] gnu: Add llvm-15 Maxim Cournoyer
2022-11-13 5:01 ` [bug#59237] [PATCH 2/3] gnu: Add clang-runtime-15 Maxim Cournoyer
2022-11-13 5:02 ` [bug#59237] [PATCH 3/3] gnu: Add clang-15 Maxim Cournoyer
2022-11-15 10:33 ` Ludovic Courtès [this message]
2022-11-15 10:34 ` [bug#59237] [PATCH 0/3] Add LLVM/Clang 15.0.4 Ludovic Courtès
2022-11-15 10:28 ` Ludovic Courtès
2022-11-16 14:18 ` [bug#59237] [PATCH v2 0/5] Add LLVM/Clang 15 Maxim Cournoyer
2022-11-16 14:18 ` [bug#59237] [PATCH v2 1/5] gnu: Add llvm-15 Maxim Cournoyer
2022-11-16 14:18 ` [bug#59237] [PATCH v2 2/5] gnu: Add clang-runtime-15 Maxim Cournoyer
2022-11-16 14:18 ` [bug#59237] [PATCH v2 3/5] gnu: Add clang-15 Maxim Cournoyer
2022-11-16 14:18 ` [bug#59237] [PATCH v2 4/5] gnu: Add libomp-15 Maxim Cournoyer
2022-11-16 14:18 ` [bug#59237] [PATCH v2 5/5] gnu: Add clang-toolchain-15 Maxim Cournoyer
2022-11-16 15:21 ` [bug#59237] [PATCH 0/3] Add LLVM/Clang 15.0.4 Ludovic Courtès
2022-11-16 19:16 ` bug#59237: " Maxim Cournoyer
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=8735ako6bx.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=59237@debbugs.gnu.org \
--cc=maxim.cournoyer@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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.