From: cubexyz@gmail.com (Mark Longridge)
Subject: [TUHS] recreating bj.s for Unix v5
Date: Fri, 12 Jun 2015 16:16:20 -0400 [thread overview]
Message-ID: <CADxT5N543fP++gdHAWkJRcRYQ3YgZm+LFxjsxig5tNijz6X9bQ@mail.gmail.com> (raw)
In-Reply-To: <20150612200043.4F65218C0C0@mercury.lcs.mit.edu>
> I missed some. It also wants quest1, quest2 and quest5 (and maybe more).
> This may present a bit of a problem, as I can't find any trace of them
> anywhere, and will have to work out from the source what their arguments,
> etc are, what they do, etc.
>
> I wonder how on earth the 2.11 people got this to assemble? (Or maybe they
> didn't?)
>
> Noel
You gave me a good hint :)
in 2.11bsd:
cd /usr/src/games/pdp
su
make bj
which does:
as -o bj.o etc.s bj.s us.s
ld -o bj bj.o -lc
the executable seems to work OK.
I tried to assemble it in v5 and it actually does assemble but then
gives "Memory fault -- Core dumped" when trying to run it.
I was wrong about .even, the v5 assembler does understand it. It might
just be easier to modify a later version of bj.c so the v5 compiler
could use it.
On 6/12/15, Noel Chiappa <jnc at mercury.lcs.mit.edu> wrote:
> > From: Noel Chiappa
>
> > another assembler source file, which contains the following routines
> > which are missing from bj.s:
>
> I missed some. It also wants quest1, quest2 and quest5 (and maybe more).
> This may present a bit of a problem, as I can't find any trace of them
> anywhere, and will have to work out from the source what their arguments,
> etc are, what they do, etc.
>
> I wonder how on earth the 2.11 people got this to assemble? (Or maybe they
> didn't?)
>
> Noel
>
next prev parent reply other threads:[~2015-06-12 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 20:00 Noel Chiappa
2015-06-12 20:16 ` Mark Longridge [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-12 19:31 Noel Chiappa
2015-06-12 18:39 Noel Chiappa
2015-06-12 19:01 ` Mark Longridge
2015-06-12 22:46 ` Greg 'groggy' Lehey
2015-06-12 18:23 Mark Longridge
2015-06-15 5:14 ` Lars Brinkhoff
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=CADxT5N543fP++gdHAWkJRcRYQ3YgZm+LFxjsxig5tNijz6X9bQ@mail.gmail.com \
--to=cubexyz@gmail.com \
/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).