From: zimoun <zimon.toutoune@gmail.com>
To: 28690@debbugs.gnu.org
Cc: rekado@elephly.net, post@thomasdanckaert.be, ludo@gnu.org,
dave.love@manchester.ac.uk, roel@gnu.org
Subject: [bug#28690] provide a lib output for boost
Date: Thu, 13 Jan 2022 16:45:20 +0100 [thread overview]
Message-ID: <86sftriqr3.fsf@gmail.com> (raw)
In-Reply-To: <87d164b36m.fsf@albion.it.manchester.ac.uk> (Dave Love's message of "Tue, 03 Oct 2017 17:34:41 +0100")
Hi,
This patch #28690 [1] is about adding an output to boost. The aim is to
reduce the closure size.
The last message if from Dec. 2017 and indicates some issues.
1: <http://issues.guix.gnu.org/issue/28690>
On Tue, 03 Oct 2017 at 17:34, Dave Love <dave.love@manchester.ac.uk> wrote:
> I mentioned elsewhere noticing the large size of boost in closures.
> I've now realized what the problem was with making a lib output, and
> done one, as below. However, presumably it should have a dependency of
> out on lib for compatibility, and I don't know the right way to do that.
>
> The lib package is 17MiB, and the headers are 108MiB.
Now, the size is:
--8<---------------cut here---------------start------------->8---
$ guix size boost
store item total self
/gnu/store/rwv6khi7hg3hrhij9kimxh53mvg8ksd9-boost-1.77.0 262.0 149.7 57.1%
/gnu/store/7sik9fp2ffvnr7l01s423x4r5pn75rf9-icu4c-69.1 110.7 38.0 14.5%
/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33 38.3 36.6 14.0%
/gnu/store/90lbavffg0csrf208nw0ayj1bz5knl47-gcc-10.3.0-lib 71.7 33.4 12.7%
/gnu/store/ggrih6fgnflxs6k87m8q2l9ky0za8y1z-bash-static-5.1.8 1.7 1.7 0.6%
/gnu/store/72kpdqplq4nc87fm7ch47kxy3nlkzsyx-xz-5.2.5 73.7 1.1 0.4%
/gnu/store/vx6vfbmmazvfi7vp8xyjn2mcyylvw9gn-bash-minimal-5.1.8 39.3 1.0 0.4%
/gnu/store/w6zv2mz56wyxr471q38a3cmzm4iqimy8-bzip2-1.0.8 73.1 0.4 0.2%
/gnu/store/2i0zpa5w320y8m4zbqk1va8vs6dbawv0-zlib-1.2.11 71.9 0.2 0.1%
total: 262.0 MiB
--8<---------------cut here---------------end--------------->8---
Note that that’s a core-updates change.
--8<---------------cut here---------------start------------->8---
$ guix refresh -l boost | cut -f1 -d':'
Building the following 4921 packages would ensure 7338 dependent packages are rebuilt
--8<---------------cut here---------------end--------------->8---
On Mon, 04 Dec 2017 at 09:19, Thomas Danckaert <post@thomasdanckaert.be> wrote:
>>> Meanwhile I'll try to build those 97 packages, stay tuned ;-)
>>
>> have you been able to build some of these packages to verify that this
>> patch is fine?
>
> I tried to build them all, but only a few packages built successfully (those).
> Most packages probably just need boost:lib added to their inputs (I already
> fixed a few in my local tree), but sometimes the build fails for other
> reasons, and verifying them all takes time (the list includes things like
> vigra and libreoffice).
>
> I should have some time in the holiday period, but help is welcome :)
>
> The updated list and a few patches are on my other computer, I'll post them
> when I get home.
Therefore, if I understand correctly, some work remains. The question
is: is it worth to complete such work about adding more outputs to
boost?
WDYT?
Cheers,
simon
next prev parent reply other threads:[~2022-01-13 16:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 16:34 [bug#28690] provide a lib output for boost Dave Love
2017-10-11 8:39 ` Roel Janssen
2017-10-19 10:57 ` Dave Love
2017-10-19 14:19 ` Roel Janssen
2017-10-20 12:58 ` Ludovic Courtès
2017-10-20 13:21 ` Thomas Danckaert
2017-10-20 16:14 ` Ludovic Courtès
2017-10-22 16:50 ` Dave Love
2017-10-22 19:03 ` Ludovic Courtès
2017-10-24 13:28 ` Thomas Danckaert
2017-10-24 15:30 ` Ludovic Courtès
2017-12-03 23:07 ` Ricardo Wurmus
2017-12-04 8:19 ` Thomas Danckaert
2017-10-20 16:09 ` Dave Love
2017-10-20 20:14 ` Ludovic Courtès
2017-10-19 12:52 ` Thomas Danckaert
2017-10-20 9:20 ` Dave Love
2017-10-20 9:46 ` Thomas Danckaert
2017-10-20 15:34 ` Dave Love
2022-01-13 15:45 ` zimoun [this message]
2022-02-03 2:30 ` zimoun
2022-06-23 10:01 ` zimoun
2022-06-23 11:35 ` Thomas Danckaert via Guix-patches
2022-10-08 15:06 ` bug#28690: " zimoun
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86sftriqr3.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=28690@debbugs.gnu.org \
--cc=dave.love@manchester.ac.uk \
--cc=ludo@gnu.org \
--cc=post@thomasdanckaert.be \
--cc=rekado@elephly.net \
--cc=roel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.