From: Efraim Flashner <efraim@flashner.co.il>
To: "Haugen, Kjetil" <Kjetil.Haugen@amd.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: limited compiler-rt support in llvm-15?
Date: Sun, 26 Feb 2023 14:03:49 +0200 [thread overview]
Message-ID: <Y/tKpT6PCB2nnC8t@3900XT> (raw)
In-Reply-To: <IA1PR12MB646051C38383F756B2481857F6A59@IA1PR12MB6460.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
On Tue, Feb 21, 2023 at 12:22:55AM +0000, Haugen, Kjetil via wrote:
> [AMD Official Use Only - General]
>
> Hello!
>
> I'm in the process creating guix packages for rocm using upstream clang. I noticed that for clang-runtime-15, guix now explicitly deletes all static libraries which makes the packages with -rtlib=compiler-rt fail due to missing libclang_rt.builtins-x86_64.a. Is there any particular reason why guix made that change between clang-runtime-14 and clang-runtime-15? I'd like to propose to revert that change. I know I can always create my own clang-runtime-15 variant, but I was hoping to avoid the additional complexity of maintaining custom versions of clang-runtime and all the packages that depend on it.
>
> Thanks,
> KJ
I looked through the git history and I didn't see anything obvious about
why they were deleted. I assume it was to save space. If it does break
linking like that then I don't see a reason why it couldn't be changed.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-02-26 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 0:22 limited compiler-rt support in llvm-15? Haugen, Kjetil via
2023-02-26 12:03 ` Efraim Flashner [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=Y/tKpT6PCB2nnC8t@3900XT \
--to=efraim@flashner.co.il \
--cc=Kjetil.Haugen@amd.com \
--cc=help-guix@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.
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).