From bb701610aaa645644bfa046b30711fc5acb7c6c2 Mon Sep 17 00:00:00 2001 From: Mike Frysinger Date: Sat, 26 Jan 2013 13:44:47 -0500 Subject: buildsys: allow the toolchain to search its dirs for kernel headers Setting KERNEL_HEADERS up to the exact path all the time is a pita, especially when the toolchain is often times already configured to do the right thing. So if the user has set that to "", don't force any specific paths. Signed-off-by: Mike Frysinger --- extra/Configs/Config.in.arch | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'extra/Configs/Config.in.arch') diff --git a/extra/Configs/Config.in.arch b/extra/Configs/Config.in.arch index e97786b81..6d93433dc 100644 --- a/extra/Configs/Config.in.arch +++ b/extra/Configs/Config.in.arch @@ -192,7 +192,7 @@ config UCLIBC_HAS_LONG_DOUBLE_MATH config KERNEL_HEADERS string "Linux kernel header location" - default "/usr/include" + default "" help The kernel source you use to compile with should be the same as the Linux kernel you run your apps on. uClibc doesn't even @@ -203,6 +203,8 @@ config KERNEL_HEADERS but then run on Linux 2.0.x, lchown will be compiled into uClibc, but won't work at all. You have been warned. + If you don't set this, we'll assume the toolchain can find them. + config UCLIBC_UCLINUX_BROKEN_MUNMAP bool depends on !ARCH_USE_MMU -- cgit v1.2.3