From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 17741 invoked from network); 7 May 2022 03:33:29 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 7 May 2022 03:33:29 -0000
Received: from maat.thinktankworkspaces.com ([45.79.94.76]) by 9front; Fri May  6 23:31:29 -0400 2022
Message-ID: <384CF35CA4C61F6FDEB2121471D1CFE8@thinktankworkspaces.com>
To: 9front@9front.org
Date: Fri, 06 May 2022 20:31:28 -0700
From: william@thinktankworkspaces.com
In-Reply-To: <04E55A65712E9EF43F9B05C54D4725AC@eigenstate.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: agile RESTful cache module wrapper 
Subject: Re: [9front] build iso from arm64
Reply-To: 9front@9front.org
Precedence: bulk

Thanks. I miss the obvious. 

I have another question. Looks like I need to add
an entry form arm64. But where is the kernel for arm64?

It can't be 9pc64 that is AMD, bcm is for pi i.e broadcom. I know 9pc64 is wrong but ran it anyways.

%.arm64.iso:
	@{
	objtype=arm64
	kernel=/n/src9/$objtype/9pc64
	mk $target.$pid.pc.iso
	mv $target.$pid.pc.iso $target
	}

/sys/lib/dist
cpu% mk /tmp/9front.$objtype.iso
@{
objtype=arm64
kernel=/n/src9/$objtype/9pc64
mk /tmp/9front.arm64.iso.60008.pc.iso
mv /tmp/9front.arm64.iso.60008.pc.iso /tmp/9front.arm64.iso
}
mk: don't know how to make '/n/src9/arm64/9pc64' in directory /sys/lib/dist
mk: @{ objtype=arm64 kernel=/n/src9/$objtype/9pc64 ...  : exit status=rc 60010: rc 60012: mk 60013: error

I went to /sys/src9/386 and kernel boot and a few other files exist for 386. I suspect I have
more leg work to do 

Is it /sys/src/9/kw or is it /sys/src/9/omap

I guess this is the next decision its an ARM Cortex-A53 

I guess I need set CONF and try running make in either of those directories. Then copy the kernel over.  



Quoth ori@eigenstate.org:
> Quoth william@thinktankworkspaces.com:
> > Here are the exact commands I ran followed by the error at the end. I must be missing
> > a step or not understanding something. 
> > 
> > 	cd /
> > 	for(i in /sys/src/cmd/7[acl]){cd $i && mk install}
> > 
> > build remaining arm64 binaries
> > 
> > 	cd /sys/src
> > 	objtype=arm64 
> > 	mk install
> > 
> > Building an ISO
> > 
> > Put your root file system into /n/src9
> > 
> > 	bind /root /n/src9
> > 
> > Put your hg repository there
> > 
> > 	bind -ac /dist/plan9front /n/src9
> > 
> > Build the iso
> > 
> > 	cd /sys/lib/dist
> > 	mk /tmp/9front.$objtype.iso
> > 
> > mk: don't know how to make '/tmp/9front.arm64.iso' in directory /sys/lib/dist
> > 
> > 
> 
> I don't think we have any arm images that boot from an iso,
> so we have no rules for building it.
> 
> pick a target that exists -- say, amd64 or 386.
> 
> read the mkfile to see what we can build.
> 
> 
> 
>