From: Joseph Myers <joseph@codesourcery.com>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: <libc-alpha@sourceware.org>, <stgraber@stgraber.org>,
<serge@hallyn.com>, <fweimer@redhat.com>
Subject: Re: [PATCH 2/2 v2] openpty: use TIOCGPTPEER to open slave side fd
Date: Mon, 28 Aug 2017 12:22:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1708281221480.17216@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20170828121106.2629-1-christian.brauner@ubuntu.com>
On Mon, 28 Aug 2017, Christian Brauner wrote:
> + /* Try to allocate slave fd solely based on master fd first. */
> + slave = ioctl (master, TIOCGPTPEER, O_RDWR | O_NOCTTY);
You still need the #ifdef. openpty is used on non-Linux systems, and the
oldest kernel headers supported for building glibc are 3.2.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-08-28 12:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 14:21 [PATCH 1/2] openpty: close slave pty fd on error Christian Brauner
2017-08-26 14:21 ` [PATCH 2/2] openpty: use TIOCGPTPEER to open slave side fd Christian Brauner
2017-08-28 7:34 ` Florian Weimer
2017-08-28 11:14 ` Christian Brauner
2017-08-28 11:39 ` Joseph Myers
2017-08-28 12:11 ` [PATCH 2/2 v2] " Christian Brauner
2017-08-28 12:22 ` Joseph Myers [this message]
2017-08-28 12:34 ` Andreas Schwab
2017-08-28 12:51 ` [PATCH 2/2 v3] " Christian Brauner
2017-08-29 9:07 ` [PATCH 1/2] openpty: close slave pty fd on error Florian Weimer
2017-08-29 13:46 ` [PATCH 1/2 v4] " Christian Brauner
2017-08-29 13:46 ` [PATCH 2/2 v4] openpty: use TIOCGPTPEER to open slave side fd Christian Brauner
2017-08-29 14:00 ` [PATCH 1/2 v4] openpty: close slave pty fd on error Andreas Schwab
2017-08-29 14:12 ` Christian Brauner
2017-08-29 14:31 ` [PATCH 1/2 v5] " Christian Brauner
2017-08-29 14:31 ` [PATCH 2/2 v5] openpty: use TIOCGPTPEER to open slave side fd Christian Brauner
2017-09-10 17:45 ` [PATCH 1/2 v5] openpty: close slave pty fd on error Christian Brauner
2017-09-20 10:53 ` Christian Brauner
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=alpine.DEB.2.20.1708281221480.17216@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=christian.brauner@ubuntu.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=serge@hallyn.com \
--cc=stgraber@stgraber.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).