Hello, This patch arranges to always have <toplevel-build-dir>/gcc/include in the -I flags for libgcc on VxWorks. This directory contains user accessible header files provided by gcc so is legitimate and needed in many cases.
This is implicitly achieved with -B when building a regular cross compiler, but there's no such -B when cross compiling libraries as part of a canadian build. We have been using this for months on gcc-6 and gcc-7 ports to a large variety of VxWorks 6 and 7 configurations, and Rasmus reported that it is fixing the exact same issue for them (https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00120.html) Committing to mainline, Olivier 2018-06-07 Olivier Hainque <hain...@adacore.com> * libgcc/config/t-vxworks (LIBGCC_INCLUDES): Add -I$(MULTIBUILDTOP)../../gcc/include. * libgcc/config/t-vxworks7: Likewise. Reformat a bit to match the t-vxworks layout.
0002-Refine-I-flags-for-VxWorks-libgcc.patch
Description: Binary data
