2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/config-language.txt.
7 bool "Target CPU has a memory management unit (MMU)"
8 default y if !ARCH_HAS_NO_MMU
10 If your target CPU does not have a memory management unit (MMU),
11 then answer N here. Normally, Linux runs on systems with an MMU.
12 If you are building a uClinux system, answer N.
14 Most people will answer Y.
16 config UCLIBC_HAS_FLOATS
17 bool "Enable floating point number support"
20 This option allows you to entirely omit all floating point number
21 support from uClibc. This will cause floating point functions like
22 strtod() to be omitted from uClibc. Other floating point functions,
23 such as printf() and scanf() will still be included in the library,
24 but will not contain support for floating point numbers.
26 Answering N to this option can reduce the size of uClibc. Most people
30 bool "Target CPU has a floating point unit (FPU)"
31 depends on UCLIBC_HAS_FLOATS
34 If your target CPU does not have a Floating Point Unit (FPU) or a
35 kernel FPU emulator, but you still wish to support floating point
36 functions, then uClibc will need to be compiled with soft floating
37 point support (-msoft-float). If your target CPU does not have an
38 FPU or an FPU emulator within the Linux kernel, then you should
41 Most people will answer Y.
44 bool "Enable full C99 math library support"
45 depends on UCLIBC_HAS_FLOATS
48 If you want the uClibc math library to contain the full set C99
49 math library features, then answer Y. If you leave this set to
50 N the math library will contain only the math functions that were
51 listed as part of the traditionla POSIX/IEEE 1003.1b-1993 standard.
52 Leaving this option set to N will save around 35k on an x86 system.
54 If your applications require the newer C99 math library functions,
58 string "Compiler Warnings"
61 Set this to the set of gcc warnings you wish to see while compiling.
64 string "Linux kernel header location"
65 default "/usr/src/linux"
67 The kernel source you use to compile with should be the same as the
68 Linux kernel you run your apps on. uClibc doesn't even try to achieve binary
69 compatibility across kernel versions. So don't expect, for example, uClibc
70 compiled with Linux kernel 2.0.x to implement lchown properly, since 2.0.x
71 can't do that. Similarly, if you compile uClibc vs Linux 2.4.x kernel headers,
72 but then run on Linux 2.0.x, lchown will be compiled into uClibc, but won't
73 work at all. You have been warned.
75 config UCLIBC_UCLINUX_BROKEN_MUNMAP
77 depends on !UCLIBC_HAS_MMU
82 depends on !UCLIBC_HAS_MMU