zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Jun T <takimoto-j@kba.biglobe.ne.jp>
Cc: zsh-workers@zsh.org
Subject: Re: Hang in E01 due to zpty on OpenBSD
Date: Mon, 4 Apr 2022 13:21:34 +0200	[thread overview]
Message-ID: <CAHYJk3Tp4e14-3VNpJdt5hKG2shCKdcvWa0_TwQ0sfC4TjbS7A@mail.gmail.com> (raw)
In-Reply-To: <4BCAE950-2D78-415A-88C3-8362946DC74C@kba.biglobe.ne.jp>

On 4/4/22, Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
>
> Please try the following patch.
>
> diff --git a/Src/Modules/zpty.c b/Src/Modules/zpty.c
> index dfd2a2a7a..cdab1d8e1 100644
> --- a/Src/Modules/zpty.c
> +++ b/Src/Modules/zpty.c
> diff --git a/configure.ac b/configure.ac
> index 8bba78c56..6aae71300 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -2441,6 +2441,18 @@ int ptsname();]],
> [[]])],[ac_cv_use_dev_ptmx=no],[ac_cv_use_dev_ptmx=yes])])
>     fi
>  fi
>
> +dnl On (some) OpenBSD, it seems openpty() is the only reliable way to get
> pty.
> +AH_TEMPLATE([HAVE_OPENPTY],
> +[Define to 1 if openpt() is available on OpenBSD])

Missing y here in openpty.


-- 
Mikael Magnusson


  reply	other threads:[~2022-04-04 11:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 21:42 Matthew Martin
2022-04-04  1:04 ` Bart Schaefer
2022-04-04  2:34   ` Matthew Martin
2022-04-04  3:49     ` Matthew Martin
2022-04-04  8:34       ` Jun T
2022-04-04 11:21         ` Mikael Magnusson [this message]
2022-04-04 13:16         ` Matthew Martin
2022-04-06  5:48           ` Jun T
2022-04-06 12:53             ` Matthew Martin
2022-04-06 20:12               ` Bart Schaefer
2022-04-07  3:47               ` Jun T
2022-04-07  4:52                 ` Matthew Martin
2022-04-08  7:51                   ` Jun T
2022-04-04  2:39 ` Jun T
2022-04-04  2:51   ` Matthew Martin

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=CAHYJk3Tp4e14-3VNpJdt5hKG2shCKdcvWa0_TwQ0sfC4TjbS7A@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).