aboutsummaryrefslogtreecommitdiffstats
path: root/toolchain
diff options
context:
space:
mode:
authorHauke Mehrtens <hauke@hauke-m.de>2022-09-12 00:31:43 +0200
committerHauke Mehrtens <hauke@hauke-m.de>2022-09-12 23:34:10 +0200
commitb21ddbfa18cd1e437e31dc0fa29408721a186c2a (patch)
tree2f2e69c97bb3090041d4bb9de8aff073b3b74a93 /toolchain
parent9403810c020cca136149973a3929bf77a1f501aa (diff)
downloadupstream-b21ddbfa18cd1e437e31dc0fa29408721a186c2a.tar.gz
upstream-b21ddbfa18cd1e437e31dc0fa29408721a186c2a.tar.bz2
upstream-b21ddbfa18cd1e437e31dc0fa29408721a186c2a.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>
Diffstat (limited to 'toolchain')
-rw-r--r--toolchain/Config.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/toolchain/Config.in b/toolchain/Config.in
index fb14006055..6d3cc0a200 100644
--- a/toolchain/Config.in
+++ b/toolchain/Config.in
@@ -169,6 +169,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