Hello, This fixes an oversight which causes make all-gcc to fail for --target=*vxworksae or vxworksmils, a regression introduced by the recent VxWorks7 related updates.
Thanks @Martin for opening the PR. Both AE and MILS variants resort to a common config/vxworksae.h, which misses a definition of VX_CPU_PREFIX expected by port specific headers. The change just provides the missing definition. Tested by checking that I could reproduce the failure for powerpc-wrs-vxworksae, then that all-gcc passes after the patch for powerpc-wrs-vxworksae, x86-wrs-vxworksae and powerpc-wrs-vxworksmils. With Kind Regards, Olivier 2021-03-19 Olivier Hainque <hain...@adacore.com> gcc/ PR target/99660 * config/config/vxworksae.h (VX_CPU_PREFIX): Define.
diff --git a/gcc/config/vxworksae.h b/gcc/config/vxworksae.h index 0f9b55357892..86d1923b718f 100644 --- a/gcc/config/vxworksae.h +++ b/gcc/config/vxworksae.h @@ -64,6 +64,10 @@ along with GCC; see the file COPYING3. If not see /* Both kernels and RTPs have the facilities required by this macro. */ #define TARGET_POSIX_IO +/* The AE/653 system headers all predate the introduction of _VX_ prefixes + ahead of CPU families of macros. */ +#define VX_CPU_PREFIX "" + /* A VxWorks 653 implementation of TARGET_OS_CPP_BUILTINS. */ #define VXWORKS_OS_CPP_BUILTINS() \ do \