From: Artem Novikov <novikovag@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan9 from scratch
Date: Tue, 11 Jan 2011 09:57:47 +0000 [thread overview]
Message-ID: <1eff6c13-3bd3-44c0-9587-514cba0083e1@f20g2000vbc.googlegroups.com> (raw)
In-Reply-To: <AANLkTi=K74PzvFVrzeyJaZ6H_V4Zj0Fs-WiP=+qRMOL8@mail.gmail.com>
On 11 янв, 02:01, nicklafo...@gmail.com (Nick LaForge) wrote:
> I'm curious: do you plan on executing the output of 8c and 8l in an
> environment as strange as one the you are building in? You could try
> building only programs and then try executing those, i.e., by using
> one of
>
> http://www.chunder.com/plan9/9ee.htmlhttp://swtch.com/9vx/
>
> If you just want an x86 kernel, I think it begs the question. The
> distribution comes with x86 binaries, and rebuilding the whole system
> is as simple as mk.
>
> Anyway, you may be shocked by this if you come from a linux background
> where complilation is viewed as some sort of sacrificial ritual.
>
> Nick
>
> On 1/10/11, Artem Novikov <noviko...@gmail.com> wrote:
>
>
>
>
>
>
>
> > I want to build Plan9 from scratch under Windows/*NIX.
> > I built working (seems :) toolchain (yacc, 8a, 8c, 8l) under Windows
> > XP using Open Watcom Compiller.
> > Has anyone done something similar?
Thanks all.
May be building from scratch seems strange, but it only fo my Plan9 OS
researching.
I think building OS using only the source code good for a much better
understanding of Plan9.
P.S.
=) Nick, no, 8* for cross-compilation purpose.
next prev parent reply other threads:[~2011-01-11 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 10:01 Artem Novikov
2011-01-10 18:18 ` Nick LaForge
2011-01-11 9:57 ` Artem Novikov [this message]
2011-01-10 18:29 ` Skip Tavakkolian
2011-01-10 19:09 ` Charles Forsyth
2011-01-11 8:23 ` Peter Penzin
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=1eff6c13-3bd3-44c0-9587-514cba0083e1@f20g2000vbc.googlegroups.com \
--to=novikovag@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).