🚀 go-pugleaf

As a challenge, I tried compiling gcc-2.6.3 (with binutils-2.5.2) on a
Tek workstation (20 MHz 68020 with 68881 FPU) and the Green Hill's C
compiler.  I will warn you that I've taken ONE basic compiler class
(where we only covered front-end issues), and don't know a whole lot
about COFF or other link-level stuff.  I had an assembly programming
class in m68k once, too.  I *do* know C though.  :^)

Having said that, I would still like to get gcc running on these
beasts!  If you would like to help me, I'd be much obliged.  (If you
think I'm crazy and know it will be next to impossible, I'd still like
to hear from you--I can always use encouragement. :^)

Here's where I'm at so far:

  o I've compiled these gnu utilities on the workstation thus far:
    sed-2.05, grep-2.0, gzip-1.2.4, bison-1.24, flex-2.5.2.  And
    tcsh-6.06 for good measure (and my sanity).

  o Gcc didn't have a default target for m68k-tektronix-bsd, so I picked
    something fairly close--m68k-hp-bsd* (or hp300bsd).  Everything
    compiled beautifully until we got to ./xgcc compiling enquire.c into
    an object file--the native assembler barfed.

  o So I tried to configure and compile binutils-2.5.2.  The configure
    script stopped at ld--no default target.  So again I picked hp300bsd
    as a close approximation.  I built and installed the binutils, and
    everyone seemed to be happy (seemed being the key word).

  o Reconfigured gcc with --with-gnu-as and --with-gnu-ld, making sure
    that /usr/local/bin was FIRST in my path.  This time we got past the
    enquire.c to enquire.o stage, but instead barfed when trying to link
    enquire.o to an executable.  The error message said something about
    not being able to find the "a.out-hp300bsd" format.

  o I figured this was probably right since I wasn't on an hp300bsd
    machine, so I hacked at binutils some more and removed all
    references to hp300bsd (instead changing them to tek4300bsd).
    Compiled & installed binutils again.  Gcc stopped again when linking
    enquire.o--couldn't find the "a.out-tek4300bsd" format.  *D'OH*

Of course, the native linker (/bin/ld) doesn't recognize the format of
the new ./xgcc object file (hell, it doesn't even know about the -L
flag!).

Am I spinning my wheels?   Grasping at straws?  Or am I fairly close?
If you can help, please drop me a line or post to the newsgroup.
Thanks!

Dave
-- 
David D. Kilzer              \ ``My goal is to carry the Macintosh torch and
ddkilzer@iastate.edu         /   save computer users from the Gates of Hell.''
Computer Engineer 5          \                 Guy Kawasaki
Iowa State University, Ames  /       Recently-appointed Apple Fellow