From: wkt@tuhs.org (Warren Toomey)
Subject: [Unix-jun72] assembling ux.s
Date: Tue, 29 Apr 2008 16:31:01 +1000 [thread overview]
Message-ID: <20080429063101.GA23694@minnie.tuhs.org> (raw)
In-Reply-To: <Pine.BSI.4.64.0804281528090.20990@malasada.lava.net>
On Mon, Apr 28, 2008 at 03:33:25PM -1000, Tim Newsham wrote:
> I am trying out apout using the "1972_stuff" binaries. When using
> "as" to assemble "ux" (e10-01 through e10-02) it gives an error
> "m 0024" (multiply-defined label) for the line:
>
> mount: .=.+1024.
>
> I assume this is because the assembler has predefined the "mount"
> system call (I ran across this earlier when using my system call
> table sys.s with ux with the v7 assembler).
It does look like this is the case. The manual says that syscall names
are pre-defined, and in these source fragments from 1972, you can see
that as definitely knows about mount and open:
http://minnie.tuhs.org/UnixTree/1972_stuff/s1/frag37.html
http://minnie.tuhs.org/UnixTree/1972_stuff/s1/frag22.html
I've sent an e-mail to Dennis to see if he can remember what the procedure
was to rebuild the kernel from the assembly source.
Cheers,
Warren
prev parent reply other threads:[~2008-04-29 6:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 1:33 Tim Newsham
2008-04-29 6:31 ` Warren Toomey [this message]
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=20080429063101.GA23694@minnie.tuhs.org \
--to=wkt@tuhs.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).