>>> Here's what I've retested on x86_64-linux-gnu and, slightly adjusted for >>> gcc-13, on arm-vx7r2. Ok to install? >> >> OK
Thanks Jonathan! >> If there's any chance of getting the vxworks system headers fixed to >> work with GCC properly, that would be nice. That would be nice for sure. From the vendor end, that seems very unlikely, unfortunately: VxWorks, for a variety of targets, used to come with both gcc and llvm system toolchains, with active support for the two possibilities in system headers. Also Diab to some extent. Over the years, even if there are still bits around in some headers, active support for gnu toolchains was removed and I don't see that it will be reintroduced. Jakub suggested: > Fixincludes? > That seems like the standard way to workaround bugs in system headers on > proprietary targets. Indeed, although we'd really rather avoid relying on that as much/as long as we reasonably can due to a few specifities of common VxWorks setups. Since VxWorks 7, for a given base distrib for a target environment, different users or projects configure kernels specifically to include such or such feature, and this tailors the exposed set of system headers. Relying on fixincludes would require installing an instance of gcc for each such configuration, resinstalling (or re-mkheaders) every time a kernel configuration change takes place, on hosts where users might need to go through sysadmins for compiler updates. This would be, I'm afraid, a significant regression in usability. Olivier
