[comp.sys.amiga.tech] Need a linker for my GCC Amiga cross-compiler

ronbo@vixen.uucp (Ron Hitchens) (10/18/90)

[]
     I have the GNU C compiler (gcc) working as an Amiga cross-compiler on
my Sun 3/60, but I'm missing the last essential link in the chain.  I need
a linker for Amiga binaries that I can run on the Sun.  Does anybody know of
any PD sources for a linker?  I've looked through the Fish catalog, but the
only alternative linker available seems to be BLINK, which doesn't have the
source available.  Can anybody help me out?

     I'm currently compiling the .o files on the Sun, then running the Manx
linker to produce the final executable (I can produce either Manx or standard
Amiga format binaries) and my Amiga has an ethernet board, so I don't need to
transfer anything.  I'd like to do the entire process on the Sun side, since
I'm using a standard 1000, which compiles pretty slow.  I could probably
write my own linker, I wrote a simple one in college long ago, but that's
a fairly hefty project.  I'd like to start from something that is already
working if possible.

     For those who are interested, I am running gcc unmodified, the only thing
I did was make up a config header which specified the Amiga-standard register
usage and a few other tweaks.  I use the same gas assembler binary for both
Sun and Amiga compilations.  The magic is in a binary file translation
program I wrote which converts unix a.out files to Amiga format.

     A few months ago, I remember someone posting an article (from Europe
I think) saying that they were working on a gcc port for the Amiga.  I'd
appreciate it if that person (or persons) would get in touch with me.

     Now, to avoid any confusion, I *DO NOT* have gcc running on the Amiga
at the present time.  I could probably produce a binary of gcc for the
Amiga right now (assuming the Manx linker or BLINK wouldn't barf on it),
but I don't have any use for that right now.  My desire for the time being
is to cross-compile on the Sun to produce Amiga binaries.  Making an Amiga
runnable gcc would require some care since it's so huge (the 68020 binary of
CC1 (the actual compiler itself) is about half a megabyte, a binary compiled
for a plain 68000 would probably be bigger).  One would need to link it so
that it would scatter-load in managable hunks, and I'm sure it allocates
humongous gobs of memory for symbol tables and such.

     Anyway, if anyone can help me find a linker in source form I can use,
I'd appreciate it.  Thanks.

[This Internet address may no longer be valid, it forwarded to vixen anyway]
-- 
Ron Hitchens    /-O-O   | ronbo@vixen.uucp			- Smart uucp
  Sleepless     C  >    | ...!cs.utah.edu!caeco!vixen!ronbo	- Stupid uucp
    Software       ~    | hitchens@cs.utexas.edu		- Internet
"To be is to do" -Socrates  "To do is to be" -Sartre  "Do be do be do" -Sinatra