From: Pierre Neidhardt <mail@ambrevar.xyz>
To: 42576@debbugs.gnu.org
Subject: [bug#42576] Acknowledgement ([PATCH 1/2] gnu: llvm: Move dynamic libraries to a separate "lib" output.)
Date: Tue, 28 Jul 2020 12:07:59 +0200 [thread overview]
Message-ID: <877duodkao.fsf@ambrevar.xyz> (raw)
In-Reply-To: <handler.42576.B.159593032321168.ack@debbugs.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
This patch is meant for core-updates since it rebuilds every LLVm
dependent, so more than 1000+ packages. I've only tested against master
though.
It's not ready yet.
Since LLVM@10 takes a long time to compile, it's cumbersome to iterate
against it.
Instead, I found out that LLVM@3.5 builds much faster and the `pure'
package is a great candidate for testing.
I've added ("llvm" llvm-3.5 "lib") to the dependencies of pure.
But ("llvm" llvm-3.5) must be included as a native input because that's
where the C headers (include) files are.
The end result still depends on llvm "out" because the .so files has
references to the headers.
We could move the headers to a separate output, but LLVM@10 headers are
17MiB big already, so I'd rather not include them in the closure of
every package.
Any idea how to remove them?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-07-28 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 9:58 [bug#42576] [PATCH 1/2] gnu: llvm: Move dynamic libraries to a separate "lib" output Pierre Neidhardt
2020-07-28 10:03 ` [bug#42576] [PATCH 2/2] gnu: llvm-3.9.1: Move libraries to " Pierre Neidhardt
[not found] ` <handler.42576.B.159593032321168.ack@debbugs.gnu.org>
2020-07-28 10:07 ` Pierre Neidhardt [this message]
2020-08-01 10:59 ` [bug#42576] [PATCH 1/2] gnu: llvm: Move dynamic libraries to a separate " Danny Milosavljevic
2020-08-01 11:18 ` Pierre Neidhardt
2020-08-07 18:09 ` Jakub Kądziołka
2020-08-08 8:49 ` Pierre Neidhardt
2021-09-24 0:41 ` Sarah Morgensen
2021-09-24 7:10 ` Pierre Neidhardt
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=877duodkao.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=42576@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).