On Tue, 2018-11-20 at 13:03 +0100, Jan Kiszka wrote:
On 19.11.18 23:17, Nobuhiro Iwamatsu wrote:
Hi,Hmm, that message does not yet read to me like a blocker. It's a list of
We can see the current hardware problem of armel / armhf from the following.
2018年11月19日(月) 17:53 Jan Kiszka <jan.kiszka@...>:On 19.11.18 09:14, SZ Lin (林上智) wrote:
Hi,Huh?! Can we support them with hardware to avoid that?
Please find the logs of CIP meeting last week in below link:
#action Confirm the next official CIP kernel announcement in TSC meeting.
#action Make sure armhf is available in Debian 10 (or not)
I also wonder what makes this buster-specific. The issues with the build
environment should be generic, shared with supported arm* for stretch or even older.
Of course, but including them in buster will add another 2 years to the
time these architectures have to be supported.
For what it's worth, the SIGMINSTKSZ issue is fixed in 4.20 by:
22839869f21a signal: Introduce COMPAT_SIGMINSTKSZ for use in compat_sys_sigaltstack
24951465cbd2 arm64: compat: Provide definition for COMPAT_SIGMINSTKSZ
We need to get these added to Debian's 4.19 kernel at least, but they
might also be candidates for 4.19-stable.
Again, if there is any concrete thing we could help with here, please let us
discuss proposals at TSC level and with Debian folks. armhf is critical for most
of us, and that for quite a few years onward.
Ben Hutchings, Software Developer Codethink Ltdhttps://www.codethink.co.uk/
Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom