29 May
2003
29 May
'03
1:27 a.m.
On Thu, 29 May 2003, Brian Hechinger wrote:
oops, forgot to mention that part. if i Ctrl/E from
within the running
simulator, it crashes sim and takes the controlling xterm/rxvt with it.
If the xterm/rxvt seems 'hosed' but is still running, try running
"reset",
which should reset the terminal to 'sane' characteristics. I'm guessing
the problem is that the keyboard gets set to 'noecho' or 'raw' mode or
something.
i should try doing this telnetting in from a remote
machine i think.
Or, if possible, try it from a virtual/serial console - without a
windowing system in the way.
IMHO that's *always* a good thing. it has really
opened my eyes to the fact
that your average opensource coder has been so coddled by the whole gcc/x86
platform that they have really started to make stupid mistakes and even
stupider assumptions about things. the most common assumption is that a
void pointer and an int pointer is the same size. which just happens to be
Do you mean void * and int (not a pointer)? All pointers should be the
same size... (Sorry, I'm being pedantic.)
true in 32-bit land, but totally hoses those of us who
live in 64-bit land.
hell, even the code that autoconf generates for tests makes that assumption.
First, you need a "BIN" subdir, and then "make BIN/vax". I think I
remember reading this in a readme somewhere... I usually end up just
being lazy and running a "make all". Anyways, who knows when I'll want to
play with an IBM 1401 sim :).
Pat
--
Purdue University ITAP/RCS
Information Technology at Purdue
Research Computing and Storage
http://www.itap.purdue.edu/rcs/
the problem, but hiding it under a mass of
additional messages.
how do i build just the VAX portion? 'make vax' does nothing, and 'make
VAX'
says everything is up to date. that's one ugly makefile, so it's kinda hard
to interpret for someone who hasn't messed with makefiles in years.