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-10-03 19:51:50 +0200
commit938ae926751672cfac8fe18a1ed6f20ec40b10e5 (patch)
tree1c75b9ea94952cb055232871b4d1c5d5b88434c5 /toolchain
parent8f72f5e4c0c368902087cc26f7d16ff4f012ed1b (diff)
downloadupstream-938ae926751672cfac8fe18a1ed6f20ec40b10e5.tar.gz
upstream-938ae926751672cfac8fe18a1ed6f20ec40b10e5.tar.bz2
upstream-938ae926751672cfac8fe18a1ed6f20ec40b10e5.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 b21ddbfa18cd1e437e31dc0fa29408721a186c2a)
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 366f5c8b48..f02790ba52 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