public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Paillard <spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Simon Paillard <spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Subject: [PATCH] resolver.3: RES_DEBUG not accessible with default build
Date: Mon,  4 Mar 2013 23:45:19 +0100	[thread overview]
Message-ID: <1362437119-28677-1-git-send-email-spaillard@debian.org> (raw)

See http://bugs.debian.org/692136

For the record, it seems this has been the case in glibc since a while
committer	Roland McGrath <roland-mXXj517/zsQ@public.gmane.org>
Sat, 18 Feb 1995 01:27:10 +0000 (01:27 +0000)
commit	28f540f45bbacd939bfd07f213bcad2bf730b1bf
http://repo.or.cz/w/glibc.git/blob/28f540f45bbacd939bfd07f213bcad2bf730b1bf:/resolv/res_init.c
---
 man3/resolver.3 |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/man3/resolver.3 b/man3/resolver.3
index af532f7..390d51b 100644
--- a/man3/resolver.3
+++ b/man3/resolver.3
@@ -184,7 +184,8 @@ True if
 has been called.
 .TP
 .B RES_DEBUG
-Print debugging messages.
+Print debugging messages.  This option needs glibc to be build with debugging 
+enabled, which is not the default.
 .TP
 .B RES_AAONLY
 Accept authoritative answers only.
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2013-03-04 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04 22:45 Simon Paillard [this message]
     [not found] ` <1362437119-28677-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-03-05  6:47   ` [PATCH] resolver.3: RES_DEBUG not accessible with default build Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1362437119-28677-1-git-send-email-spaillard@debian.org \
    --to=spaillard-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox