[Bug 1811296] Re: libc++ files version mismatch

2020-03-30 Thread Mike Purvis
Not sure about older released, but it's actually broken again already— currently in Sid, the versions of gcc-arm-none-eabi and libstdc++-arm- none-eabi are both 15:8-2019-q3-1: https://packages.debian.org/sid/devel/gcc-arm-none-eabi

[Bug 1811296] Re: libc++ files version mismatch

2020-03-13 Thread Alistair Buxton
Fixed in libstdc++-arm-none-eabi-newlib 15:8-2019-q3-1+12build1 Is this still a problem for older releases? Is there anything that could be done to prevent this happening in the future? ** Changed in: gcc-arm-none-eabi (Ubuntu) Status: Confirmed => Invalid ** Changed in:

[Bug 1811296] Re: libc++ files version mismatch

2020-03-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gcc-arm-none-eabi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811296

[Bug 1811296] Re: libc++ files version mismatch

2020-03-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libstdc++-arm-none-eabi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1811296] Re: libc++ files version mismatch

2020-02-26 Thread Mike Purvis
This was working correctly on Ubuntu Focal with gcc-arm-none-eabi (15:7-2018-q2-6) and libstdc++-arm-none-eabi-newlib (15:7-2018-q2-5+12). However, now that gcc-arm-none-eabi is at 15:8-2019-q3-1, it's broken again. Hopefully the newlib package will get a rebuild prior to release which should