From: Yoann Padioleau <pad@fb.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Cross-compiling Plan 9
Date: Mon, 14 Jul 2014 22:31:47 +0000 [thread overview]
Message-ID: <4C90CE19-CCA6-4DD4-AD45-3C49CF7B24AB@fb.com> (raw)
In-Reply-To: <20140715001950.0812ce52@zinc.9fans.fr>
[-- Attachment #1: Type: text/plain, Size: 1583 bytes --]
Yep, I did exactly the same. With kencc+a-few-patches+plan9port+few-symlinks
you can easily cross compile plan9.
See my kencc fork changes:
https://github.com/aryx/fork-kencc/commits/master
(and my fork 9 fork:
https://github.com/aryx/fork-plan9
)
On Jul 14, 2014, at 3:19 PM, David du Colombier <0intro@gmail.com<mailto:0intro@gmail.com>> wrote:
Since I am building everything on Unix, and am using the Unix shell
(bash in my case), I had to rewrite much of the mkfile rules,
specifically ones that deal with loops, conditionals and substituting
outputs from commands. Because all those rules are simple, this was a
trivial task. I also needed to change sed programs embedded all over
the place to be understandable to my systems sed.
If you use plan9port's mk, you can define MKSHELL=rc in the
mkfiles, instead of translating them to bash.
In the same way, you can place $PLAN9/bin at the beginning of
your PATH to use plan9port's sed instead of the Unix one.
In my side, I also tried to compile the Plan 9 programs and
libraries on Unix using Charles' toolchain. It was working
pretty fine. The main issue I encountered was the lack of
support for long Runes in his version.
Thus, I simply copied the related code from Plan 9:
https://urldefense.proofpoint.com/v1/url?u=http://www.9legacy.org/9legacy/patch/kencc-rune.diff&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=%2FN9d7W2LRwZks3eyFNLr8Q%3D%3D%0A&m=aLQhZbTqEOAyTguyZu3l8YOQdmbEXDfuDYgNH8idwCE%3D%0A&s=a9410420e661f42c32ce304cfe6fe28914154e91a65bd7c1c9e5f0f341b0b146
--
David du Colombier
[-- Attachment #2: Type: text/html, Size: 2621 bytes --]
prev parent reply other threads:[~2014-07-14 22:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 13:13 Aleksandar Kuktin
2014-07-05 13:22 ` Jacob Todd
2014-07-05 14:02 ` Charles Forsyth
2014-07-07 17:41 ` Yoann Padioleau
2014-07-07 18:21 ` Skip Tavakkolian
2014-07-07 18:33 ` Charles Forsyth
2014-07-07 18:34 ` Charles Forsyth
2014-07-07 18:47 ` Yoann Padioleau
2014-07-07 19:51 ` Charles Forsyth
2014-07-08 0:10 ` Aleksandar Kuktin
2014-07-09 0:10 ` kokamoto
2014-07-09 7:24 ` Charles Forsyth
2014-07-10 2:02 ` kokamoto
2014-07-13 19:11 ` Aleksandar Kuktin
2014-07-14 22:19 ` David du Colombier
2014-07-14 22:31 ` Yoann Padioleau [this message]
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=4C90CE19-CCA6-4DD4-AD45-3C49CF7B24AB@fb.com \
--to=pad@fb.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).