diff options
| author | Olivier Hainque <hainque@adacore.com> | 2022-03-07 10:55:29 +0000 |
|---|---|---|
| committer | Olivier Hainque <hainque@adacore.com> | 2022-10-02 09:33:00 +0000 |
| commit | b83b13331aca413cac80b0d7928b59b12e490f93 (patch) | |
| tree | 67447da0e70362f20c21098cc0f090f73a71d683 /gcc | |
| parent | 2f26f5b584856927337728ddc598c44f1426fa32 (diff) | |
| download | gcc-b83b13331aca413cac80b0d7928b59b12e490f93.zip gcc-b83b13331aca413cac80b0d7928b59b12e490f93.tar.gz gcc-b83b13331aca413cac80b0d7928b59b12e490f93.tar.bz2 | |
Adjust LIBGCC2_INCLUDES for VxWorks and augment comment
Investigating the reasons for libgcc build failures in a canadian
context, orthogonally to the recent update of vxcrtstuff, exposed
interesting differences in the way include search paths are managed
between a regular Linux->VxWorks cross build and a canadian setup
building a Windows->VxWorks toolchain in a Linux environment.
This change augments the comment attached to LIBGCC2_INCLUDE in
libgcc/config/t-vxworks to better describe the parameters at play.
It also adjusts the addition of options for gcc/include and
gcc/include-fixed to minimize the actual differences for libgcc
in the two kinds of configurations.
2022-03-06 Olivier Hainque <hainque@adacore.com>
libgcc/
* config/t-vxworks (LIBGCC2_INCLUDE): Augment comment. Move
-I options for gcc/include and gcc/include-fixed at the end
and make them -isystem.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions