On 10/05/2017 11:49 PM, Christoph Biedl wrote:
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.
I wouldn't call that simple if-clause complexity.
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.
gcc bugs aren't usually something that get fixed promptly, in particular when talking about non-mainstream architectures like m68k. I will mark busybox as "Not-For-Us" for the time being now because I don't want to be chasing this package over this and keep building it manually so that debian-installer doesn't break for us. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@xxxxxxxxxx `. `' Freie Universitaet Berlin - glaubitz@xxxxxxxxxxxxxxxxxxx `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
