summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBernhard Reutner-Fischer <rep.dot.nop@gmail.com>2007-09-20 12:07:10 +0000
committerBernhard Reutner-Fischer <rep.dot.nop@gmail.com>2007-09-20 12:07:10 +0000
commit5b542bd0aaef3f9d2f6f2b2a9140db7b16b46f33 (patch)
tree6ec2f2544d07b12f074be46fc8bd624f77a21650
parent430586dbc6318350eb8423ee0ebc4d46139cc08b (diff)
- spelling fix
-rw-r--r--extra/Configs/Config.in4
1 files changed, 2 insertions, 2 deletions
diff --git a/extra/Configs/Config.in b/extra/Configs/Config.in
index 0c277f928..30b4a4c89 100644
--- a/extra/Configs/Config.in
+++ b/extra/Configs/Config.in
@@ -423,7 +423,7 @@ config MALLOC_GLIBC_COMPAT
help
The behavior of malloc(0) is listed as implementation-defined by
SuSv3. Glibc returns a valid pointer to something, while uClibc
- normally return a NULL. I personally feel glibc's behavior is
+ normally returns NULL. I personally feel glibc's behavior is
not particularly safe, and allows buggy applications to hide very
serious problems.
@@ -431,7 +431,7 @@ config MALLOC_GLIBC_COMPAT
return a live pointer when someone calls malloc(0). This pointer
provides a malloc'ed area with a size of 1 byte. This feature is
mostly useful when dealing with applications using autoconf's broken
- AC_FUNC_MALLOC macro (which redefines malloc as rpl_malloc if it
+ AC_FUNC_MALLOC macro (which redefines malloc as rpl_malloc if it
does not detect glibc style returning-a-valid-pointer-for-malloc(0)
behavior). Most people can safely answer N.