> On 17 Dec 2021, at 14:16, Rasmus Villemoes wrote:
>
> There's no yvals.h header in VxWorks 5.5, so I'm not sure I need to have
> an opinion on this one.
I wasn't sure about the situation on 5.5 but the fix just
wont apply if there's no yvals.h around anyway.
Cheers,
Olivier
On 17/12/2021 13.14, Olivier Hainque wrote:
> Hello,
>
> yvals.h on VxWorks expects the toolchain to provide its own
> version of the header, which we don't do.
>
> The attached patch adds a fixincludes hack to arrange to fallback
> on the common system definitions instead.
>
> We were able to g
Hello,
yvals.h on VxWorks expects the toolchain to provide its own
version of the header, which we don't do.
The attached patch adds a fixincludes hack to arrange to fallback
on the common system definitions instead.
We were able to get a successful complete build with c++ and
libstdc++ after th
