From: Peter Stephenson <pws@csr.com>
To: Zsh workers <zsh-workers@sunsite.dk>
Subject: Re: zpty on HP/UX
Date: Mon, 15 Mar 2004 17:11:31 +0000 [thread overview]
Message-ID: <5306.1079370691@csr.com> (raw)
In-Reply-To: "Oliver Kiddle"'s message of "Mon, 15 Mar 2004 17:55:20 +0100." <3716.1079369720@trentino.logica.co.uk>
Oliver Kiddle wrote:
> I've got zpty to work on HP/UX. I looked at pts(7) and tried the example
> in there.
>
> Basically it needs the ioctl streams stuff but not the ttcompat bit. See
> the patch below to see what needed removing. Note that this isn't a patch
> I intend to apply but merely in indication of the changes. We need to
> sort out the #if stuff.
>
> We can put the ttcompat ioctl inside a #ifndef __hpux but the __SVR4
> part is going to cause us problems. What systems was that added to cover?
The bits marked #if ... defined(__SVR4) are really there for Solaris. I
asked if anyone knew other systems which needed the STREAMS stuff but
apparently no one did. This was my best guess as to systems which might
need it. The additional test turned out to be necessary because
allowing those ioctl's to run on some Linux systems (where STREAMS was
present) screwed things up. Linux doesn't define __SVR4.
Unless someone turns out to be a secret STREAMS expert we are stuck with
doing it machine by machine, i.e. adding __hpux where necessary.
I don't see a good reason for changing from __SVR4 for the other case.
(Does STREAMS still have a use apart from screwing things up if it isn't
handled as a special case?)
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
next prev parent reply other threads:[~2004-03-15 17:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 16:55 Oliver Kiddle
2004-03-15 17:11 ` Peter Stephenson [this message]
2004-03-16 15:07 ` PATCH: " Peter Stephenson
2004-03-16 19:47 ` Oliver Kiddle
2004-03-16 23:50 ` mneptok
2004-03-17 10:12 ` Oliver Kiddle
2004-03-17 10:23 ` PATCH: zpty on HP/UX (and Mac OS X 10.3) James Devenish
2004-03-17 11:10 ` mneptok
2004-03-17 11:34 ` Mac OS X 10.3 again [was: PATCH: zpty on HP/UX] James Devenish
2004-03-17 13:19 ` Mac OS X 10.3 again James Devenish
2004-03-17 11:19 ` PATCH: zpty on HP/UX (and Mac OS X 10.3) Oliver Kiddle
2004-03-17 13:02 ` zpty on Mac OS X 10.2 Peter Stephenson
2004-03-17 14:00 ` Oliver Kiddle
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=5306.1079370691@csr.com \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/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).