From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] no apes on the bitsy?
Date: Thu, 10 May 2001 11:35:48 -0400 [thread overview]
Message-ID: <20010510153551.3A6AD199F8@mail.cse.psu.edu> (raw)
Looks like someone forgot to update the syscall convention in
APE when it was changed in the main line. Here's a correct
/sys/src/ape/lib/ap/arm/mkfile. Replace it and
cd /sys/src/ape/lib/ap
mk install
and you should be better.
BUILTINS=
NPROC=1
SYSH=/sys/src/libc/9syscall/sys.h
all:V:
SYS=`{sed 's/#define.([A-Z0-9_]*).*/\1/' $SYSH}
for(I in $SYS) {
n=`{sed -n '/[ ]'$I'[ ]/s/.* //p' $SYSH}
echo TEXT _$I'(SB)', 1, '$0' > _$I.s
echo MOVW R0, '0(FP)' >> _$I.s
echo MOVW '$'$n, R0 >> _$I.s
echo SWI 0 >> _$I.s
echo RET >> _$I.s
}
clean:V:
rm -f _*.s
next reply other threads:[~2001-05-10 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 15:35 rob pike [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-10 15:39 rob pike
2001-05-09 6:01 nemo
2001-05-08 17:43 nemo
2001-05-08 18:51 ` Dan Cross
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=20010510153551.3A6AD199F8@mail.cse.psu.edu \
--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).