🚀 go-pugleaf

Subject: Trying to compile gcc1.40 on Tektronix 4405 machine

We've "inherited" a Tek 4405 UNIX box, and after a few successes porting
software to it, are trying out the gcc compiler version 1.40

Guess what ... serious problems.

We config.gcc'd the system to be a VAX, the only reason being that we
think the machine is probaly BSD (It's got X-Windows 10.4 on it, October
1988, which makes me doubt it could be a SYS.V machine. Anyway, it was
produced for an academic environment).

Makefile runs perfectly OK over most of the files, but we don't have any
luck at all with gnulib2.c, which generated a lot of errors referring to
invalid op-codes in the temporary .s files. After a quick bit of hunting
around in the Makefile etc, we decided that gnulib2 didn't seem to be
needed until the last stage, so we went on to stage2 ...

The command line
$ make CC=stage1/gcc -CFLAGS="-g -O -Bstage1/"
started off OK with
stage1/gcc ...[lotsa cruft] gcc.c [more cruft],
then said 
Internal Assembler Error-- Unrecognized address mode in line     clrb *(r0)
a few times, referring consistently to r0 in movb as well, then came up with
/usr/tmp/cc$$.s(line number): Error: Invalid operand [and invalid op-code]

A few invalid register expressions were mixed up in there for good measure.

Basically I think we've got a problem related to the assembler on the
system not liking the choice of VAX (the Tek is, I think, an 86000, so
why am I surprised?)

Does anyone know what alternative system-type we can use with config.gcc,
or what hacks we can put in the code to help along?

Dave Palmer    <dpalmer@uk.ac.kingston>
Computer Support,
Faculty of Technology,
Kingston Polytechnic,
U.K.
+44 81-547-2000 x2911