public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 12098] New: various man pages give incorrect _XOPEN_SOURCE define
Date: Mon, 24 Nov 2008 23:04:56 -0800 (PST)	[thread overview]
Message-ID: <bug-12098-11311@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=12098

           Summary: various man pages give incorrect _XOPEN_SOURCE define
           Product: Documentation
           Version: unspecified
     KernelVersion: N/A
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
        AssignedTo: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
        ReportedBy: crimsun-NvWE5tsZCrFbyg9Ma2u3fg@public.gmane.org


Latest working kernel version: N/A
Earliest failing kernel version: N/A
Distribution: Ubuntu 9.04
Hardware Environment: N/A
Software Environment: man-pages 3.13
Problem Description: Forwarded from Ubuntu #181673
(https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/181673).  Steve
Bellovin reports that "#define _XOPEN_SOURCE" is incorrectly given for various
man pages (e.g., bsd_signal, confstr, crypt, encrypt, getdate, grantpt,
ptsname, strptime, swab, unlockpt, wcwidth) instead of "#define _XOPEN_SOURCE
600".

Steps to reproduce: Inspect the man page for any of above given examples.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
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:[~2008-11-25  7:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  7:04 bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
     [not found] ` <bug-12098-11311-V0hAGp6uBxO456/isadD/XN4h3HLQggn@public.gmane.org/>
2008-11-25 14:22   ` [Bug 12098] various man pages give incorrect _XOPEN_SOURCE define bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r

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=bug-12098-11311@http.bugzilla.kernel.org/ \
    --to=bugme-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@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