zsh-workers
 help / color / mirror / code / Atom feed
From: Matthew Martin <phy1729@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: Hang in E01 due to zpty on OpenBSD
Date: Mon, 4 Apr 2022 08:16:08 -0500	[thread overview]
Message-ID: <YkrvmNPJwCRPZ0Ud@CptOrmolo.darkstar> (raw)
In-Reply-To: <4BCAE950-2D78-415A-88C3-8362946DC74C@kba.biglobe.ne.jp>

On Mon, Apr 04, 2022 at 05:34:09PM +0900, Jun T wrote:
> 
> > 2022/04/04 12:49, Matthew Martin <phy1729@gmail.com> wrote:
> > 
> > OpenBSD has gutted the pty route and strongly prefers openpty over
> > posix_openpt. Is there a correct way link the zpty module against
> > libutil?
> 
> Please try the following patch.

I had tried a similar patch, but since openpty is in libutil, that needs
to be linked in which is why I have the dlopen/dlsym calls in 49980.

> Replace the pattern (in configure.ac)
> openbsd*)
> by
> openbsd7*)
> or such if openpty() should be used only on specific versions of OpenBSD.

I would only support OpenBSD-current unless anyone objects. Each release
gets a corresponding snapshot of the ports tree and then only security
updates are accepted for that version.


  parent reply	other threads:[~2022-04-04 13:16 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
2022-04-04 13:16         ` Matthew Martin [this message]
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=YkrvmNPJwCRPZ0Ud@CptOrmolo.darkstar \
    --to=phy1729@gmail.com \
    --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).