On 02/12/2021 16.29, Olivier Hainque wrote: > Hi Rasmus, > > Some new on this. > >> On 20 Nov 2021, at 09:07, Olivier Hainque <hain...@adacore.com> wrote: >> >> I'll check how our build sequence proceeds. > > Turns out our build succeeds thanks to the presence > of a vendor version of stdint.h in the VxWorks6/7 header dirs > and we're lucky that the need to pre-include yvals.h isn't > showing up during the libraries' build. > > It is of course not good to use one version during the build > of libraries then install an alternate version that will be > used by programs afterwards. > > The attached patch achieves the same kind of thing you > initiated, only reusing a method previously introduced > for glimits.h instead of adding a new use_gcc_stdint value, > which seems a bit less intrusive to me. > > This introduces an indirect dependency on the VxWorks version.h > for vxcrtstuff objects, for which we then need to apply the same > tricks as for libgcc2 regarding include paths (to select the system > header instead of the gcc one). > > I have had a few succesful builds and tests with this, > for both VxWorks 6 and VxWorks 7 configurations.
Reverting my fix and applying this on top of my gcc-11.2 based branch seems to work. I haven't used the compiler for building or running any modules (don't have the hardware handy), but I've done an 'objdump -d' comparison on all the generated host binaries and target libraries with no diff. So OK by me. Thanks, Rasmus
