From: Rutger Helling <rhelling@mykolab.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 38336@debbugs.gnu.org
Subject: bug#38336: ‘wine64-staging’ is very expensive to build
Date: Tue, 03 Dec 2019 09:17:56 +0100 [thread overview]
Message-ID: <b77cff590a2120ff1799db182fd688d9@mykolab.com> (raw)
In-Reply-To: <87r21z7bg8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2085 bytes --]
Hi Ludo,
Sorry for the late reply. I'm not really active anymore in Guix
development for various reasons.
Wine needs a whole 32-bit dependency chain to be able to run both 32-bit
and 64-bit code, since a Wine that can only run 64-bit code is
considered useless. That is why the package is unfortunately so large. I
don't think there's anything that can be done about that.
A couple of binaries are also copied, not just JSON files. That is where
the 32-bit dependencies come from.
On 2019-11-23 00:12, Ludovic Courtès wrote:
> Hello,
>
> I noticed that 'wine64-staging' is our most expensive package to build.
> Initially I was surprised because it only has a couple of nodes more in
> its <package> object than 'wine-staging':
>
> --8<---------------cut here---------------start------------->8---
> ludo@ribbon ~/src/guix$ guix graph wine-staging |grep 'label = ' |wc -l
> 509
> ludo@ribbon ~/src/guix$ guix graph wine64-staging |grep 'label = ' |wc -l
> 511
> --8<---------------cut here---------------end--------------->8---
>
> However, that single additional node leads to the duplication of the
> whole derivation graph on x86_64-linux:
>
> --8<---------------cut here---------------start------------->8---
> ludo@ribbon ~/src/guix$ guix graph -t derivation wine-staging |grep 'label = ' |wc -l
> 2738
> ludo@ribbon ~/src/guix$ guix graph -t derivation wine64-staging |grep 'label = ' |wc -l
> 4598
> --8<---------------cut here---------------end--------------->8---
>
> This is because 'wine-staging' has a hard-coded '#:system "i686-linux"',
> whereas 'wine64-staging' is (unsurprisingly :-)) built on x86_64-linux.
>
> (The same problem happens with 'wine' vs. 'wine64'.)
>
> Likewise, 'guix size wine64' shows that every dependency appears twice
> (one 32-bit, one 64-bit), and thus the total size is twice that of
> 'wine'.
>
> Rutger, is there something that can be done to avoid this? Apparently
> only JSON files are copied from 'wine-staging' into 'wine64-staging',
> but maybe they refer to 32-bit shared libraries or something?
>
> Thanks,
> Ludo'.
[-- Attachment #2: Type: text/html, Size: 2820 bytes --]
next prev parent reply other threads:[~2019-12-03 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 23:12 bug#38336: ‘wine64-staging’ is very expensive to build Ludovic Courtès
2019-12-03 8:17 ` Rutger Helling [this message]
2019-12-03 9:07 ` 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=b77cff590a2120ff1799db182fd688d9@mykolab.com \
--to=rhelling@mykolab.com \
--cc=38336@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).