unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <m.othacehe@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 39941@debbugs.gnu.org
Subject: bug#39941: Disk-image size increase on core-updates.
Date: Wed, 11 Mar 2020 15:45:24 +0100	[thread overview]
Message-ID: <87zhcnympn.fsf@gmail.com> (raw)
In-Reply-To: <87a74nhstf.fsf@gnu.org>


Hey,

> Could you find out (perhaps by looking at ‘guix graph -t references’)
> what is referencing these two cross-compilers?

Turns out on master,

--8<---------------cut here---------------start------------->8---
guix size `guix build guile|grep -v debug`
--8<---------------cut here---------------end--------------->8---

returns ~124 MiB, while,

--8<---------------cut here---------------start------------->8---
guix size `guix build --target=aarch64-linux-gnu guile|grep -v debug`
--8<---------------cut here---------------end--------------->8---

returns ~523 MiB.

When building the native guile, only the "lib" output of gcc is
kept. When cross-compiling, the whole cross-compiler is dragged down (as
there's only "out" defined for cross-gcc).

That does not explain the sudden increase, but this is still quite
unfortunate :p

Thanks,

Mathieu

  reply	other threads:[~2020-03-11 14:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06  7:37 bug#39941: Disk-image size increase on core-updates Mathieu Othacehe
2020-03-10  9:22 ` Mathieu Othacehe
2020-03-11 14:25   ` Ludovic Courtès
2020-03-11 14:45     ` Mathieu Othacehe [this message]
2020-03-11 20:33       ` Ludovic Courtès
2020-03-12  8:06         ` Mathieu Othacehe
2020-03-14 10:54         ` Mathieu Othacehe
2020-03-14 12:30           ` Marius Bakke
2020-03-15 11:21             ` Mathieu Othacehe
2020-03-15 17:13               ` Ludovic Courtès
2020-03-17 11:28                 ` Mathieu Othacehe
2020-03-24 10:54                   ` Ludovic Courtès
2020-03-24 17:01                     ` Mathieu Othacehe
2020-03-25 21:34                       ` 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=87zhcnympn.fsf@gmail.com \
    --to=m.othacehe@gmail.com \
    --cc=39941@debbugs.gnu.org \
    --cc=ludo@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).