From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: cross-arm-none-eabi*: update to 9.2, rework to include libgcc.a and libstdc++, newlib: build nano
Date: Sat, 28 Dec 2019 23:02:57 +0100 [thread overview]
Message-ID: <20191228220257.Rca0DrJ0b68v1Q48DRt3vV1p45_a4DMjwtAy9LOwVCs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17827@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/17827#issuecomment-569454526
Comment:
the only changes i can think of would be separating the target debug info in separate `-dbg` packages for `libstdc++` and `newlib`, however besides saving some space locally, the benefit of that is questionable and needs manual work in the template (as host `strip`/`objcopy` cannot be used) - so I probably won't bother for the time being. For the final target hardware executable, you can just strip the final thing, which will get rid of all the intermediate debug info with the same effect.
next prev parent reply other threads:[~2019-12-28 22:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 22:56 [PR PATCH] cross-arm-none-eabi*: update to 9.2, rework to include libgcc.a and libstdc++ voidlinux-github
2019-12-28 1:19 ` [PR PATCH] [Updated] " voidlinux-github
2019-12-28 1:22 ` voidlinux-github
2019-12-28 15:24 ` [PR PATCH] [Updated] [wip] " voidlinux-github
2019-12-28 16:28 ` [PR PATCH] [Updated] [wip] cross-arm-none-eabi*: update to 9.2, rework to include libgcc.a and libstdc++, newlib: build nano voidlinux-github
2019-12-28 16:39 ` voidlinux-github
2019-12-28 16:39 ` voidlinux-github
2019-12-28 20:51 ` voidlinux-github
2019-12-28 21:55 ` voidlinux-github
2019-12-28 22:02 ` voidlinux-github [this message]
2019-12-28 23:49 ` voidlinux-github
2020-01-04 1:21 ` [PR PATCH] [Merged]: " voidlinux-github
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=20191228220257.Rca0DrJ0b68v1Q48DRt3vV1p45_a4DMjwtAy9LOwVCs@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).