From: Christoph Biedl <debian.axhn@manchmal.in-ulm.de>
To: Steve McIntyre <steve@einval.com>, 877735@bugs.debian.org
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Roger Shimizu <rogershimizu@gmail.com>,
Debian m68k <debian-68k@lists.debian.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS
Date: Thu, 5 Oct 2017 23:49:52 +0200 [thread overview]
Message-ID: <1507237676@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <20171005164054.k3tln4hduzmaw4tb@tack.einval.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
Steve McIntyre wrote...
> On Thu, Oct 05, 2017 at 06:12:46PM +0200, John Paul Adrian Glaubitz wrote:
> >Hmm, ok. Is that currently actually a concern? If I'm seeing that correctly,
> >the "-Os" here only saved us around 200k. Does that already make a difference
> >on armel?
>
> Massively so, yes. Lots of the armel platforms that people care about
> have very limited space for kernel and initramfs.
Indeed. When we (KiBi, Chris and I) discussed maintaining busybox at
DebConf, such size concerns were on the list of things to keep in mind.
For that reason we will enable more applets upon justified request only.
About that particular issue I'd really like to avoid a per-architecture
switch in busybox. It adds complexity and works around a problem
instead of solving it. So please take this to gcc first unless you've
already done so. And let us know if you get the impression this won't
get fixed soon-ish - breaking an architecture still beats packaging
principles.
Christoph
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-10-05 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <150715899716.21351.14956363415364529265.reportbug@stretch64.physik.fu-berlin.de>
2017-10-05 7:25 ` Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS John Paul Adrian Glaubitz
2017-10-05 15:55 ` Roger Shimizu
2017-10-05 16:12 ` John Paul Adrian Glaubitz
2017-10-05 16:40 ` Steve McIntyre
2017-10-05 21:49 ` Christoph Biedl [this message]
2017-10-05 23:09 ` John Paul Adrian Glaubitz
2017-10-05 16:38 ` Steve McIntyre
2017-10-05 19:52 ` John Paul Adrian Glaubitz
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=1507237676@msgid.manchmal.in-ulm.de \
--to=debian.axhn@manchmal.in-ulm.de \
--cc=877735@bugs.debian.org \
--cc=debian-68k@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@vger.kernel.org \
--cc=rogershimizu@gmail.com \
--cc=steve@einval.com \
/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