On Thu, Nov 13, 2008 at 04:35:41PM -0800, [email protected] wrote:
>Author: vda
>Date: 2008-11-13 16:35:40 -0800 (Thu, 13 Nov 2008)
>New Revision: 24034
>Modified: trunk/uClibc/extra/Configs/Config.in
>===================================================================
>--- trunk/uClibc/extra/Configs/Config.in 2008-11-14 00:34:02 UTC (rev
>24033)
>+++ trunk/uClibc/extra/Configs/Config.in 2008-11-14 00:35:40 UTC (rev
>24034)
>@@ -772,7 +772,7 @@
> bool "BSD obsolete signal functions"
> default n
> help
>- These functions are provided as a compatibility interface for
>+ These functions are provided as a compatibility interface for
> programs that make use of the historical System V signal API.
> This API is obsolete:
> new applications should use the POSIX signal API (sigaction(2),
>@@ -1066,6 +1066,23 @@
>
> Most people will say N.
>
>+config UCLIBC_HAS_COMPAT_RES_STATE
>+ bool "Use compatible but bloated _res"
>+ default y
>+ help
>+ Answer Y if you build network utilities and they muck with resolver
>+ internals a lot (_res global structure). uclibc does not use most
>+ of _res.XXX fields, and with this option OFF they won't even exist.
>+ Which will make e.g. dig build fail.
>+ Answering N saves around 400 bytes in bss.
>+
>+config UCLIBC_HAS_EXTRA_COMPAT_RES_STATE
>+ bool "Use extra compatible but extra bloated _res"
missing
depends on UCLIBC_HAS_COMPAT_RES_STATE
here?
>+ default n
>+ help
>+ Answer Y if selecting UCLIBC_HAS_COMPAT_RES_STATE is not enough.
>+ As far as I can say, this should never be needed.
>+
> endif
_______________________________________________
uClibc mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/uclibc
