From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] 7c: compile error after sysupdate
Date: Mon, 24 Jun 2019 19:48:18 +0100 [thread overview]
Message-ID: <d61436a5-5036-4e57-846d-25f0d74f2e92@www.fastmail.com> (raw)
In-Reply-To: <45BFA44580EB5E1D05E448F9D5B01B30@felloff.net>
On Mon, Jun 24, 2019, at 10:36 AM, cinap_lenrek@felloff.net wrote:
> yes. this is not a mistake. you need to create these directories manually
> or use /sys/lib/rootstub.
okay. /arm64/include is missing from rootstub, resulting in:
7.c:10 6c: '/arm64/include' does not exist: /arm64/include/ureg.h
mk: 6c -FTVw -I/sys/src/cmd 7.c : exit status=rc 18153: 6c 18158: error
mk: date for (i ... : exit status=rc 15951: rc 18100: mk 18101: error
term% lc /arm64
bin/ lib/
it doesn't make any include dirs.
ah-ha!:
term% lc /dist/plan9front/
.hg/ .hgignore arm64/
remove; bind; hg up -C; unmount; lc /arm64/include
ape/ u.h ureg.h
good! userspace and kernel builds now complete without error.
>
> if you have mail history, you might find the 9front announcement for arm64
> with build instructions.
just checking, you know all this is happening when i'm not trying to do
anything with arm64?
term% whatis cputype objtype
cputype=amd64
objtype=amd64
would it be a good idea to have sysupdate source rootstub?
don't sleep-sysadmin, kids. i've got to clean up after running rootstub in $home .
next prev parent reply other threads:[~2019-06-24 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 9:36 cinap_lenrek
2019-06-24 13:50 ` Stanley Lieber
2019-06-24 18:48 ` Ethan Gardener [this message]
2019-06-24 19:00 ` hiro
2019-06-24 19:18 ` Ethan Gardener
2019-06-24 19:04 cinap_lenrek
2019-06-24 19:48 ` Ethan Gardener
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=d61436a5-5036-4e57-846d-25f0d74f2e92@www.fastmail.com \
--to=eekee57@fastmail.fm \
--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).