From: Andrew Simmons <kodogo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Any demand for a supported Windows version of p9port?
Date: Thu, 28 Jul 2016 13:08:29 +1200 [thread overview]
Message-ID: <052AE7BC-8AD5-4C0D-9E7A-F67F9B02905C@gmail.com> (raw)
In-Reply-To: <b3bf7751aa6fa799d7c17706cfb371ff@felloff.net>
What the subject line says.
This is not remotely intended to disrespect Sean Quinlan’s 9pm, or the guys who did pf9. I’m just asking because there are still chunks of p9p that I’d like to have under Windows. Some of the chunks I want (mostly the command line utilities, also sam, not so much acme) I’ve managed to build under Microsoft Visual Studio (note to self - wash mouth out and learn to eschew IDEs and love mk ((also, sub-note to self, don’t use syntax highlighting)))
But, and this is a large but, there are parts of p9port that seem to be dependent on the Unix world - unix pipes for one, the stuff about sigjmp for another.
So, what the subject line says, but also - how much of the Unix-specific stuff in the current p9p is essential to a port to Windows?
Go in peace
James V Choate XXXVI
next prev parent reply other threads:[~2016-07-28 1:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 11:55 [9fans] Virtual Box 5.1 and Plan 9 Peter Hull
2016-07-27 23:59 ` cinap_lenrek
2016-07-28 1:08 ` Andrew Simmons [this message]
2016-07-28 1:27 ` [9fans] Any demand for a supported Windows version of p9port? Chris McGee
2016-07-28 1:41 ` Winston Kodogo
2016-07-28 5:09 ` Joseph Stewart
2016-07-28 5:34 ` Andrew Simmons
2016-07-28 8:39 ` hiro
2016-07-28 9:15 ` Staven
2016-07-28 23:53 ` Andrew Simmons
2016-07-28 10:49 ` Steve Simon
2016-07-29 0:03 ` Andrew Simmons
2016-07-28 6:34 ` [9fans] Virtual Box 5.1 and Plan 9 Matthew Veety
2016-07-28 8:36 ` hiro
2016-07-28 10:38 ` Peter Hull
2016-07-28 13:37 ` cinap_lenrek
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=052AE7BC-8AD5-4C0D-9E7A-F67F9B02905C@gmail.com \
--to=kodogo@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).