🚀 go-pugleaf

I am working on a 3b2/310 version Svr3 - version 3.2 - I just got the bins for 
gcc-2.2.2 - and am slowly installing it... gcc seems to do fine with the cpp,
the compile phases, but it fails on the linker.

Now, after a little poking and prodding, I found that the linker was trying to
include crt1.o, and crtn.o  - I found a file called specs that apparently came
with the gcc bins, and it seemed to indicated that crt1.o was the startfile
that gcc used when compiling and crtn.o was the endfile.  My machine had no
crt1.o, but it did have a crt0.o - I copied the crt0.o to crt1.o - looking 
for something similar for crtn.o, I didn't find anything - so I figured I would
just try and stuff some non-offensive function (noop) into a .o file and put
it in crtn.o - Apparently that seems to work, I can now compile and run a
classic "hello world" file - which of course makes me very happy.  

The problem:  I'm not happy just letting it remain that way, I'd prefer, for my
own piece of mind, to know what functions are normally kept in crt1.o and
crtn.o.  Anyone out there know?

-Thomas riemer