9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Aleksandar Kuktin <akuktin@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Cross-compiling Plan 9
Date: Tue,  8 Jul 2014 02:10:37 +0200	[thread overview]
Message-ID: <20140708021037.173b3173@ikilid> (raw)
In-Reply-To: <000F4E23-C3D9-481E-AF1F-48049B01E168@fb.com>

[-- Attachment #1: Type: text/plain, Size: 1896 bytes --]

>On Mon, 7 Jul 2014 17:41:35 +0000
>Yoann Padioleau <pad@fb.com> wrote:
>
> Hi,
> 
> I was able to cross compile Plan9 from MacOS which is probably quite
> similar to cross compiling from Linux.
> 
> The first thing was to compile the plan9 C compilers
> on MacOS. I used https://code.google.com/p/ken-cc/ because this fork
> of the Plan9 C compilers are easier to compile on non-plan9 OSes.
> 
> Then I installed plan9port which contained a few utilities that are
> used when compiling the plan9 kernel (/bin/rc, /bin/mk).
> 
> Then I setup a few symlinks at the root e.g.
> 
> /lib -> /home/pad/plan9/root/lib
> /386 -> /home/pad/plan9/root/386
> /sys -> /home/pad/plan9/sys
> 
> Finally I have a env.sh that I source that contains important
> environment variables: export KENCC=/home/pad/kencc
> # need to modify plan9/src/cmd/mk/shell.c and put rcshell as default
> shell export PLAN9=/usr/local/plan9
> 
> export PATH=$PLAN9/bin:$KENCC/bin:$PATH
> 
> #for 8._cp to be found and called
> PATH=$PATH:.
> 
> export objtype=386
> #export objtype=arm
> export cputype=386
> 
> Then I did a few modifications to plan9 Labs and was able to compile
> and run everything under qemu.
> 
> My forks:
> https://github.com/aryx/fork-kencc
> https://github.com/aryx/fork-plan9

Thanks, Yoann.

Ken-cc may be the missing piece of the puzzle for me, however it is a
little too early to tell. Right now I'm working on compiling the kernel
which SHOULD, theoretically, be easier then userspace since the kernel
is far, far more hermetic than the userspace.

Anyhow, I'll be sure to post the method for doing it, should I
eventually end up victorious.

-- 
Svi moji e-mailovi su kriptografski potpisani. Proverite ih.
All of my e-mails are cryptographically signed. Verify them.
--
You don't need an AI for a robot uprising.
Humans will do just fine.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]

  parent reply	other threads:[~2014-07-08  0:10 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 [this message]
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

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=20140708021037.173b3173@ikilid \
    --to=akuktin@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).