From: _ resun <saif.resun@outlook.com>
To: 9fans <9fans@9fans.net>, Charles Forsyth <charles.forsyth@gmail.com>
Subject: RE: [9fans] How can I compile c code written for plan9 in ANIS C compiler
Date: Mon, 10 Oct 2022 02:39:40 +0000 [thread overview]
Message-ID: <SI2PR03MB568995C948932FB261C8246F90209@SI2PR03MB5689.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <CAOw7k5hYGuWNA1vnAde5-om=qzN3jNuU_d4Wr=wEGsLY6zLCCA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]
Well @Charles Forsyth<mailto:charles.forsyth@gmail.com> plan9port has only for unix-like systems I was willing to get them in widows.
Actually there are lots of things from plan9 that I want to use in windows. I was thinking of some substitute for the plan9 libraries for windows. Plan9port has only for unix-like system. Is there any for windows?
Extra: If there isn’t any substitute for windows, I am interested to contribute to plan9port in near future (probably about a year). Can I do so?
Thank you.
_resun
From: Charles Forsyth<mailto:charles.forsyth@gmail.com>
Sent: Thursday, October 6, 2022 16:21
To: 9fans<mailto:9fans@9fans.net>
Subject: Re: [9fans] How can I compile c code written for plan9 in ANIS C compiler
If you look at plan9port (eg, https://9fans.github.io/plan9port/), you'll see how that's done for a good chunk of the application code of Plan 9 (using host C compilers).
It also includes versions of the Plan 9 libraries that will also compile on other systems.
Indeed, if you install plan9port you should be able to use its mk, 9c and 9l and mkfile structure to compile your Plan 9 code directly (since that's how the Plan 9 libraries are compiled in plan9port).
The main restriction is that various Plan 9 C extensions aren't available, so those need to be removed first.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T422378fc25787720-M8a6ebd83fe56e837508146ba
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 4119 bytes --]
next prev parent reply other threads:[~2022-10-10 2:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 0:15 _ resun
2022-10-06 6:45 ` Steve Simon
2022-10-06 10:21 ` Charles Forsyth
2022-10-06 11:29 ` Steve Simon
2022-10-06 12:14 ` _ resun
2022-10-10 2:39 ` _ resun [this message]
2022-10-10 3:57 ` mkf9
2022-10-10 8:50 ` Steve Simon
2022-10-11 19:32 ` ron minnich
2022-10-11 23:07 ` ron minnich
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=SI2PR03MB568995C948932FB261C8246F90209@SI2PR03MB5689.apcprd03.prod.outlook.com \
--to=saif.resun@outlook.com \
--cc=9fans@9fans.net \
--cc=charles.forsyth@gmail.com \
/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).