From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Debian m68k <debian-68k@lists.debian.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>, 877735@bugs.debian.org
Subject: Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS
Date: Thu, 5 Oct 2017 09:25:12 +0200 [thread overview]
Message-ID: <998e4cf2-07bd-cb2d-1c47-c373372ce3fe@physik.fu-berlin.de> (raw)
In-Reply-To: <150715899716.21351.14956363415364529265.reportbug@stretch64.physik.fu-berlin.de>
Hi!
On 10/05/2017 01:16 AM, John Paul Adrian Glaubitz wrote:
> Since busybox is very important to boot the system and get
> debian-installer working, I would like to ask to have the
> change from [1] reverted for m68k until we have fixed the
> potential bug in gcc which most likely mis-compiled busybox.
On second thought, I would actually recommended to revert this change
for all architectures. Size isn't so much a constraint anymore these
days, you reduce the binary by about 200k. I don't think this is worth
the risk of breaking something as fundemantal as busybox.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next parent reply other threads:[~2017-10-05 7:25 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 ` John Paul Adrian Glaubitz [this message]
2017-10-05 15:55 ` Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS 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
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=998e4cf2-07bd-cb2d-1c47-c373372ce3fe@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=877735@bugs.debian.org \
--cc=debian-68k@lists.debian.org \
--cc=linux-m68k@vger.kernel.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