[Python-apps-team] Bug#997208: firmware-microbit-micropython: FTBFS: platform.h:25:10: fatal error: cstddef: No such file or directory

[Adrian Bunk]

Control: severity 998365 serious
Control: close 997208

On Sun, Oct 24, 2021 at 12:48:33PM +0200, Ondřej Kuzník wrote:
> On Sat, Oct 23, 2021 at 09:11:58PM +0200, Lucas Nussbaum wrote:
> > Source: firmware-microbit-micropython
> > Version: 1.0.1-2
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> > 
> > 
> > Relevant part (hopefully):
> >> In file included from /<<PKGBUILDDIR>>/yotta_modules/mbed-classic/api/Ethernet.h:19,
> >>                  from /<<PKGBUILDDIR>>/yotta_modules/mbed-classic/common/Ethernet.cpp:16:
> >> /<<PKGBUILDDIR>>/yotta_modules/mbed-classic/api/platform.h:25:10: fatal error: cstddef: No such file or directory
> >>    25 | #include <cstddef>
> >>       |          ^~~~~~~~~
> >> compilation terminated.
> 
> On my bookworm system this is caused by the ARM toolchain being out of
> sync in the archive, sid/testing have:
> - gcc-arm-none-eabi 10.3 (15:10.3-2021.07-1)
> - libstdc++-arm-none-eabi from gcc 8 (15:8-2019-q3-1+13)
> 
> Where bullseye has both at 15:8-2019-q3-1+13 (and 15:8-2019-q3-1+b1).
> 
> In essence this is #953420 with different version combinations. I think
> the first step would be to mark gcc builds with Breaks for the older
> libstdc++ and vice versa. Or, if possible, submit them in lockstep.

This is #998365, so the problem has to be fixed there.

> Regards,
> Ondrej

cu
Adrian