diff options
| author | Hauke Mehrtens <hauke@hauke-m.de> | 2022-09-12 00:31:43 +0200 |
|---|---|---|
| committer | Christian Marangi <ansuelsmth@gmail.com> | 2022-12-04 16:07:33 +0100 |
| commit | 629199f6c8e0dc36484dd17e971f8c1c88b705b1 (patch) | |
| tree | 5e4196b9c042fb53e023a0b1a40f189e16e1af60 /toolchain | |
| parent | 56fd8355b078d8c9e1eb0bc0ea20900e7b46fe93 (diff) | |
| download | upstream-629199f6c8e0dc36484dd17e971f8c1c88b705b1.tar.gz upstream-629199f6c8e0dc36484dd17e971f8c1c88b705b1.tar.bz2 upstream-629199f6c8e0dc36484dd17e971f8c1c88b705b1.zip | |
toolchain: Include ./include/fortify for external musl toolchain
When building with an external toolcahin with musl also include
./include/fortify by default. This is also done when we build with the
internal toolchain using musl libc.
Without this extra include the fortify source feature is not working
when using an external musl toolchain. All binaries were compiled
without fortify source when an external musl toolchain was used. All
binaries release done by the OpenWrt project use the internal toolcahin
where fortify source is working.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit 3053045093a5c89dad970b7db3ed9f2a5be993f6)
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Diffstat (limited to 'toolchain')
| -rw-r--r-- | toolchain/Config.in | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/toolchain/Config.in b/toolchain/Config.in index 6dda9af92d..c30928854b 100644 --- a/toolchain/Config.in +++ b/toolchain/Config.in @@ -135,6 +135,7 @@ menuconfig EXTERNAL_TOOLCHAIN string prompt "Toolchain include path" if DEVEL depends on EXTERNAL_TOOLCHAIN && !NATIVE_TOOLCHAIN + default "./usr/include ./include/fortify ./include" if EXTERNAL_TOOLCHAIN_LIBC_USE_MUSL default "./usr/include ./include" help Specify additional directories searched for header files (override |