From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] build iso from arm64
Date: Fri, 06 May 2022 20:31:28 -0700 [thread overview]
Message-ID: <384CF35CA4C61F6FDEB2121471D1CFE8@thinktankworkspaces.com> (raw)
In-Reply-To: <04E55A65712E9EF43F9B05C54D4725AC@eigenstate.org>
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.
>
>
>
>
next prev parent reply other threads:[~2022-05-07 3:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 3:47 william
2022-05-06 15:34 ` ori
2022-05-07 3:31 ` william [this message]
2022-05-07 3:45 ` ori
2022-05-07 4:03 ` ori
2022-05-07 4:36 ` mkf9
2022-05-07 4:45 ` Kurt H Maier
2022-05-07 5:29 ` william
2022-05-07 13:51 ` Stanley Lieber
2022-05-07 15:14 ` Thaddeus Woskowiak
2022-05-07 18:49 ` Kurt H Maier
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=384CF35CA4C61F6FDEB2121471D1CFE8@thinktankworkspaces.com \
--to=william@thinktankworkspaces.com \
--cc=9front@9front.org \
/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).