The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: sms@2BSD.COM (Steven M. Schultz)
Subject: [pups] 2.11 on an 11/44
Date: Sun, 2 Mar 2003 22:42:00 -0800 (PST)	[thread overview]
Message-ID: <200303030642.h236g0011874@moe.2bsd.com> (raw)

Hi -

> From: Bill Gunshannon <bill at cs.scranton.edu>
> Well, the fun continues. I guess it's not going to be as simple as
> 
> When I try to build a custom kernel I get this:
> 
> cc -O -DKERNEL -DUOFS -I. -I../h -S ../sys/kern_clock.c
> /bin/ed - < SPLFIX kern_clock.s
> ?
> ?
> ?
> ?
> ?
> ----------------------

> And the "?" go on forever. Can't even break out of it.  Have to
> kill the simulation and start all over.  Anybody run into this??

	I have an extremely vague memory I might have seen it eons upon 
	eons ago but I might be imaginging it.

> Seems to be in the clock code.  Is there something I might have

	Hmmm, '?' is "ed"s error indication.   I wonder if the '?' is
	coming out of ed and not SIMH?

> missed in the CONFIG file that could cause this??  All I basicly

	Not at this stage of the build - a config file error wouldn't allow
	the first few compiles to succeed and then start causing errors
	on kern_clock.c

	One thing I did notice though was the use of 'ed' - that tells me
	the patchlevel of the system is very low (i.e. old).   'ed' was
	replaced with 'sed' which sped things up a _lot_ - and that took
	place back around #325 in 1996.

	Have you tried P11 instead of SIMH?  When I'm too lazy to fire up
	the 11/73 I use P11 to do the testing/patching and so on.   It's a
	bit a pain to configure (really arcane configfile syntax) but it works
	very well - never had a problem with it.

	Good Luck.

	Steven Schultz



             reply	other threads:[~2003-03-03  6:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03  6:42 Steven M. Schultz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-01 14:06 Norman Wilson
2003-02-27 17:06 Steven M. Schultz
2003-02-27 15:57 Fred N. van Kempen
2003-02-27 16:02 ` Bill Gunshannon
2003-02-27 15:08 Bill Gunshannon
2003-02-27 15:55 ` David Evans
2003-02-27 16:28 ` Johnny Billquist
2003-02-27 16:42   ` Bill Gunshannon
2003-02-27 16:59     ` Johnny Billquist
2003-02-27 17:33       ` Bill Gunshannon
2003-02-27 20:25         ` Bill Gunshannon
2003-03-01 21:36 ` Robin Birch

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=200303030642.h236g0011874@moe.2bsd.com \
    --to=sms@2bsd.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).