* Re: [9fans] Bitsy armpaq.proto
@ 2002-04-28 16:28 plan9
2002-04-28 15:41 ` andrey mirtchovski
0 siblings, 1 reply; 6+ messages in thread
From: plan9 @ 2002-04-28 16:28 UTC (permalink / raw)
To: 9fans
:-) Don't try it, you may be surprised...
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] Bitsy armpaq.proto
2002-04-28 16:28 [9fans] Bitsy armpaq.proto plan9
@ 2002-04-28 15:41 ` andrey mirtchovski
0 siblings, 0 replies; 6+ messages in thread
From: andrey mirtchovski @ 2002-04-28 15:41 UTC (permalink / raw)
To: 9fans
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...
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] Bitsy armpaq.proto
@ 2002-04-28 15:50 rob pike, esq.
0 siblings, 0 replies; 6+ messages in thread
From: rob pike, esq. @ 2002-04-28 15:50 UTC (permalink / raw)
To: 9fans
[-- 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...
>
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [9fans] Bitsy armpaq.proto
@ 2002-04-28 15:35 Sape Mullender
0 siblings, 0 replies; 6+ messages in thread
From: Sape Mullender @ 2002-04-28 15:35 UTC (permalink / raw)
To: 9fans
> :-) Don't try it, you may be surprised...
Make sure you install arm binaries before making paqdisk.
Watch the error messages about missing files from
processing the proto file.
Sape
^ permalink raw reply [flat|nested] 6+ messages in thread
* [9fans] Bitsy armpaq.proto
@ 2002-04-28 14:54 plan9
0 siblings, 0 replies; 6+ messages in thread
From: plan9 @ 2002-04-28 14:54 UTC (permalink / raw)
To: 9fans
Congratulations,
The Bitsy port looks better than its previous version. Just one question ..... :-)
Who stole /arm/bin/auth/fgui ?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] Bitsy armpaq.proto
@ 2002-04-28 13:56 rob pike, esq.
0 siblings, 0 replies; 6+ messages in thread
From: rob pike, esq. @ 2002-04-28 13:56 UTC (permalink / raw)
To: 9fans
> Who stole /arm/bin/auth/fgui ?
To keep the distribution small, we included binaries only for the 386.
To build all the ARM goodies,
cd /sys/src
objtype=arm
mk install
-rob
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2002-04-28 16:28 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-28 16:28 [9fans] Bitsy armpaq.proto plan9
2002-04-28 15:41 ` andrey mirtchovski
-- strict thread matches above, loose matches on Subject: below --
2002-04-28 15:50 rob pike, esq.
2002-04-28 15:35 Sape Mullender
2002-04-28 14:54 plan9
2002-04-28 13:56 rob pike, esq.
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).