9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Bitsy armpaq.proto
Date: Sun, 28 Apr 2002 11:50:48 -0400	[thread overview]
Message-ID: <bded54d2fd4840961aabbe0a4a2eecce@plan9.bell-labs.com> (raw)

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

This looks much closer to the full script.  Again for space reasons,
we didn't package binaries for the other compilers, so you must build
them first (with objtype=386).  Then you can build the libraries and
user-level programs.  But the bitsy kernel needs booting stuff, so you
must then build in /sys/src/boot/arm before you can build in
/sys/src/9/bitsy.

-rob

[-- Attachment #2: Type: message/rfc822, Size: 1899 bytes --]

From: andrey mirtchovski <andrey@lanl.gov>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Bitsy armpaq.proto
Date: Sun, 28 Apr 2002 09:41:09 -0600 (MDT)
Message-ID: <20020428093158.U563-100000@fbsd.acl.lanl.gov>


if you're talking about mk-ing the distribution, it fails because 5[acl]
binaries are not included.. something like this will succesfully compile
the bitsy port:

#!/bin/rc
objtype=386
for (i in /sys/src/cmd/5*) { cd $i && mk install }
objtype=arm
cd /sys/src/ && mk install
cd /sys/src/boot/arm && mk install
cd /sys/src/9/bitsy && mk

On Sun, 28 Apr 2002 plan9@itic.ca wrote:

>
> :-) Don't try it, you may be surprised...
>


             reply	other threads:[~2002-04-28 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-28 15:50 rob pike, esq. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-28 16:28 plan9
2002-04-28 15:41 ` andrey mirtchovski
2002-04-28 15:35 Sape Mullender
2002-04-28 14:54 plan9
2002-04-28 13:56 rob pike, esq.

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=bded54d2fd4840961aabbe0a4a2eecce@plan9.bell-labs.com \
    --to=rob@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).