Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Hang in E01 due to zpty on OpenBSD
- X-seq: zsh-workers 49986
- From: Matthew Martin <phy1729@xxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: Hang in E01 due to zpty on OpenBSD
- Date: Mon, 4 Apr 2022 08:16:08 -0500
- Archived-at: <https://zsh.org/workers/49986>
- In-reply-to: <4BCAE950-2D78-415A-88C3-8362946DC74C@kba.biglobe.ne.jp>
- List-id: <zsh-workers.zsh.org>
- Mail-followup-to: zsh-workers@xxxxxxx
- References: <YkoUwETgsrrqDeZN@CptOrmolo.darkstar> <CAH+w=7ba1fo9BdNurD9TH5MjuyYRk=-xJ0ioXo8aTt_ZCKEhLw@mail.gmail.com> <YkpZH28mfZHlsd2T@CptOrmolo.darkstar> <YkpqyANtIznaB1tC@CptOrmolo.darkstar> <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@xxxxxxxxx> 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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author