[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uclibc-cvs
Subject:    svn commit: trunk/uClibc/extra/Configs
From:       aldot () uclibc ! org (aldot at uclibc ! org)
Date:       2008-01-19 15:26:18
Message-ID: 20080119152618.76F2F12C58C () busybox ! net
[Download RAW message or body]

Author: aldot
Date: 2008-01-19 07:26:17 -0800 (Sat, 19 Jan 2008)
New Revision: 20879

Log:
- wrap superlong lines


Modified:
   trunk/uClibc/extra/Configs/Config.in.arch


Changeset:
Modified: trunk/uClibc/extra/Configs/Config.in.arch
===================================================================
--- trunk/uClibc/extra/Configs/Config.in.arch	2008-01-19 15:23:14 UTC (rev 20878)
+++ trunk/uClibc/extra/Configs/Config.in.arch	2008-01-19 15:26:17 UTC (rev 20879)
@@ -123,8 +123,8 @@
 	  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 @@
 	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


[prev in list] [next in list] [prev in thread] [next in thread]