diff options
| author | Stephanos Ioannidis <root@stephanos.io> | 2022-05-10 01:11:23 +0900 |
|---|---|---|
| committer | Chris Packham <judge.packham@gmail.com> | 2022-05-12 20:58:29 +1200 |
| commit | 1da7698b7cce647a91cbb885d1ec9da69a45a1df (patch) | |
| tree | 80d713307e86477a39699ee66082e2e5c02862d6 /samples | |
| parent | 396f23d3dee16a55e0da0ed985dab1c94c2e57a9 (diff) | |
| download | crosstool-ng-1da7698b7cce647a91cbb885d1ec9da69a45a1df.tar.gz crosstool-ng-1da7698b7cce647a91cbb885d1ec9da69a45a1df.tar.bz2 crosstool-ng-1da7698b7cce647a91cbb885d1ec9da69a45a1df.zip | |
newlib-nano: Fix include path for CT_NEWLIB_NANO_INSTALL_IN_TARGET
When `CT_NEWLIB_NANO_INSTALL_IN_TARGET=y`, the `nano.specs` file
emitted by the newlib-nano build script contains an invalid include
path, resulting in the full `newlib.h` being included instead of the
nano `newlib.h` by the application.
`=/include/newlib-nano` is not a valid path (`=` does not mean anything
and that string is taken as an include path as-is) and GCC ignores this
include path, resulting in application including the `newlib.h` from
`include/` which contains the newlib build configurations for the full
newlib.
This commit modifies the newlib-nano build script to emit a proper
newlib-nano include path relative to the `GCC_EXEC_PREFIX`.
Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions