From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Danny Milosavljevic <dannym@scratchpost.org>,
Mathieu Othacehe <othacehe@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: linux-module-builder leads to huge store items
Date: Thu, 10 Sep 2020 10:09:11 +0200 [thread overview]
Message-ID: <874ko6jbo8.fsf@inria.fr> (raw)
Hello Danny & Mathieu,
While looking for sources of contention on ci.guix.gnu.org, I found that
“linux-libre-module-builder” leads to huuuuge trees in the store;
performing deduplication on these trees takes ages, and more generally
these big trees look unreasaonble to me.
--8<---------------cut here---------------start------------->8---
$ find /gnu/store/s9md49vjambvprpp5ba3aqvhxilw0w7k-linux-libre-module-builder-5.8.8|wc -l
85604
$ du -hs /gnu/store/s9md49vjambvprpp5ba3aqvhxilw0w7k-linux-libre-module-builder-5.8.8
1.1G /gnu/store/s9md49vjambvprpp5ba3aqvhxilw0w7k-linux-libre-module-builder-5.8.8
--8<---------------cut here---------------end--------------->8---
Surely we don’t need that much just to build a kernel module. :-)
(gnu build-system linux-module) has this:
;; TODO: Only preserve the minimum, i.e. [Kbuild], Kconfig,
;; scripts, include, ".config".
Which files exactly are needed? Can we go ahead and implement this TODO?
I understand the need to “cut corners” while trying things out, but I’d
argue that this specific corner should have been restored before getting
into master.
Thanks,
Ludo’.
next reply other threads:[~2020-09-10 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 8:09 Ludovic Courtès [this message]
2020-09-10 13:04 ` linux-module-builder leads to huge store items Danny Milosavljevic
2020-09-10 16:26 ` Ludovic Courtès
2020-09-11 11:09 ` Danny Milosavljevic
2020-09-11 14:55 ` Ludovic Courtès
2020-09-11 17:44 ` Danny Milosavljevic
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=874ko6jbo8.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=othacehe@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).