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: Tue, 24 Mar 2020 18:01:05 +0100 [thread overview]
Message-ID: <87ftdxoffy.fsf@gmail.com> (raw)
In-Reply-To: <87y2rqm3ae.fsf@gnu.org>
>> +--- a/libgcc/configure
>> ++++ b/libgcc/configure
>
> I suspect this is the only file we need to patch, no? At least, we can
> remove all the m4 and m4-related Makefile.in changes and the unrelated
> ‘configure’ changes.
The configure files of the other libraries are needed too because they
end-up in the same folder:
--8<---------------cut here---------------start------------->8---
mathieu@elbruz ~/guix [env]$ ls /gnu/store/ay4agvf29mpdib4v35i557cddc8cvkja-gcc-cross-aarch64-linux-gnu-7.5.0-lib/aarch64-linux-gnu/lib/*so
/gnu/store/ay4agvf29mpdib4v35i557cddc8cvkja-gcc-cross-aarch64-linux-gnu-7.5.0-lib/aarch64-linux-gnu/lib/libasan.so
/gnu/store/ay4agvf29mpdib4v35i557cddc8cvkja-gcc-cross-aarch64-linux-gnu-7.5.0-lib/aarch64-linux-gnu/lib/libatomic.so
/gnu/store/ay4agvf29mpdib4v35i557cddc8cvkja-gcc-cross-aarch64-linux-gnu-7.5.0-lib/aarch64-linux-gnu/lib/libgcc_s.so
/gnu/store/ay4agvf29mpdib4v35i557cddc8cvkja-gcc-cross-aarch64-linux-gnu-7.5.0-lib/aarch64-linux-gnu/lib/libgomp.so
/gnu/store/ay4agvf29mpdib4v35i557cddc8cvkja-gcc-cross-aarch64-linux-gnu-7.5.0-lib/aarch64-linux-gnu/lib/libitm.so
/gnu/store/ay4agvf29mpdib4v35i557cddc8cvkja-gcc-cross-aarch64-linux-gnu-7.5.0-lib/aarch64-linux-gnu/lib/liblsan.so
/gnu/store/ay4agvf29mpdib4v35i557cddc8cvkja-gcc-cross-aarch64-linux-gnu-7.5.0-lib/aarch64-linux-gnu/lib/libssp.so
/gnu/store/ay4agvf29mpdib4v35i557cddc8cvkja-gcc-cross-aarch64-linux-gnu-7.5.0-lib/aarch64-linux-gnu/lib/libstdc++.so
/gnu/store/ay4agvf29mpdib4v35i557cddc8cvkja-gcc-cross-aarch64-linux-gnu-7.5.0-lib/aarch64-linux-gnu/lib/libtsan.so
/gnu/store/ay4agvf29mpdib4v35i557cddc8cvkja-gcc-cross-aarch64-linux-gnu-7.5.0-lib/aarch64-linux-gnu/lib/libubsan.so
--8<---------------cut here---------------end--------------->8---
But the m4 file and m4-related changes are definitely useless. I removed
them and pushed!
Thanks,
Mathieu
next prev parent reply other threads:[~2020-03-24 17:02 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
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 [this message]
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=87ftdxoffy.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).