From: Felipe Gasper <felipe@felipegasper.com>
To: "Z. Majeed" <zmajeed@sbcglobal.net>
Cc: "cygwin-developers@cygwin.com" <cygwin-developers@cygwin.com>
Subject: Re: Status of ptsname()
Date: Mon, 18 Apr 2022 15:21:32 -0400 [thread overview]
Message-ID: <4917F813-31E7-4A05-BF82-1ABEEBD081A8@felipegasper.com> (raw)
In-Reply-To: <249274291.525023.1650308956508@mail.yahoo.com>
> On Apr 18, 2022, at 15:09, Z. Majeed <zmajeed@sbcglobal.net> wrote:
>
> man ptsname says to define _XOPEN_SOURCE >= 500. I found that -D_XOPEN_SOURCE=700 works
Interesting … Cygwin’s own `man ptsname` doesn’t show that--on my system, at least?--though macOS’s does.
Or do I somehow have an outdated Cygwin man-pages?
-F
next prev parent reply other threads:[~2022-04-18 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 18:20 Felipe Gasper
2022-04-18 19:09 ` Z. Majeed
2022-04-18 19:21 ` Felipe Gasper [this message]
2022-04-18 21:15 ` Adam Dinwoodie
2022-04-18 21:39 ` Felipe Gasper
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=4917F813-31E7-4A05-BF82-1ABEEBD081A8@felipegasper.com \
--to=felipe@felipegasper.com \
--cc=cygwin-developers@cygwin.com \
--cc=zmajeed@sbcglobal.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).