Good for me, thanks Rasmus.
> On 4 Mar 2022, at 09:27, Rasmus Villemoes wrote:
>
> There doesn't seem to be any reason for this TU to include
> , and it causes errors when the resulting libstdc++ is used
> on our VxWorks 5.5 target - presumably because now libstdc++ itself
> contains an instanc
On Fri, 4 Mar 2022 at 08:28, Rasmus Villemoes wrote:
>
> There doesn't seem to be any reason for this TU to include
> , and it causes errors when the resulting libstdc++ is used
> on our VxWorks 5.5 target - presumably because now libstdc++ itself
> contains an instance of std::ios_base::Init. Whic
There doesn't seem to be any reason for this TU to include
, and it causes errors when the resulting libstdc++ is used
on our VxWorks 5.5 target - presumably because now libstdc++ itself
contains an instance of std::ios_base::Init. Which should be mostly
harmless, but apparently isn't, and from a Q
