|
|
@@ -123,8 +123,8 @@ config UCLIBC_HAS_FLOATS
|
|
|
such as printf() and scanf() will still be included in the library,
|
|
|
but will not contain support for floating point numbers.
|
|
|
|
|
|
- Answering N to this option can reduce the size of uClibc. Most people
|
|
|
- will answer Y.
|
|
|
+ Answering N to this option can reduce the size of uClibc.
|
|
|
+ Most people will answer Y.
|
|
|
|
|
|
config UCLIBC_HAS_FPU
|
|
|
bool "Target CPU has a floating point unit (FPU)"
|
|
|
@@ -172,13 +172,14 @@ config KERNEL_HEADERS
|
|
|
string "Linux kernel header location"
|
|
|
default "/usr/include"
|
|
|
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 try to achieve binary
|
|
|
- compatibility across kernel versions. So don't expect, for example, uClibc
|
|
|
- compiled with Linux kernel 2.0.x to implement lchown properly, since 2.0.x
|
|
|
- can't do that. Similarly, if you compile uClibc vs Linux 2.4.x 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.
|
|
|
+ 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
|
|
|
+ try to achieve binary compatibility across kernel versions.
|
|
|
+ So don't expect, for example, uClibc compiled with Linux kernel
|
|
|
+ 2.0.x to implement lchown properly, since 2.0.x can't do that.
|
|
|
+ Similarly, if you compile uClibc vs Linux 2.4.x 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.
|
|
|
|
|
|
config UCLIBC_UCLINUX_BROKEN_MUNMAP
|
|
|
bool
|
Bernhard Reutner-Fischer