From: jcapp@anteil.com (Jim Capp)
Subject: [Unix-jun72] Readme written: needs checking
Date: Tue, 06 May 2008 23:59:54 -0400 [thread overview]
Message-ID: <4821293A.8000909@anteil.com> (raw)
In-Reply-To: <20080507034347.GA81221@minnie.tuhs.org>
Warren,
I just did a new checkout of unix72 and it build like a charm!!!
I will go back and test the simh build again with the new instructions.
Cheers,
Jim
Warren Toomey wrote:
> On Tue, May 06, 2008 at 11:36:41PM -0400, Jim Capp wrote:
>
>> The hardest part was patching and compiling simh under Linux. I have
>> edited the various files by hand and have attached a new KE.diff.
>>
>
> Jim, Tim & I have fixed a few things up. Could you clean out your Simh
> build, re-fetch the svn tree from scratch, and try again? The Readme is
> also updated.
>
> Thanks for testing it when it was (is?) on the bleeding edge though!
>
> Warren
> _______________________________________________
> Unix-jun72 mailing list
> Unix-jun72 at tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/unix-jun72
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20080506/4bd1be78/attachment.html>
next prev parent reply other threads:[~2008-05-07 3:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 1:33 Warren Toomey
2008-05-07 2:35 ` John Cowan
2008-05-07 3:05 ` Tim Newsham
2008-05-07 3:19 ` Warren Toomey
2008-05-07 5:11 ` John Cowan
2008-05-07 6:18 ` Warren Toomey
2008-05-07 3:29 ` [Unix-jun72] simh patch fails Warren Toomey
2008-05-07 2:44 ` [Unix-jun72] Readme written: needs checking Jim Capp
2008-05-07 3:36 ` Jim Capp
2008-05-07 3:43 ` Warren Toomey
2008-05-07 3:59 ` Jim Capp [this message]
2008-05-07 4:01 ` Jim Capp
2008-05-07 5:22 ` Johan Beisser
2008-05-07 8:40 ` P.A.Osborne
2008-05-07 9:28 ` Warren Toomey
2008-05-07 10:19 ` P.A.Osborne
2008-05-07 14:11 ` Robert Tillyard
2008-05-07 14:29 ` P.A.Osborne
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=4821293A.8000909@anteil.com \
--to=jcapp@anteil.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).