🚀 go-pugleaf

I agree with Thad that the only way to do a port is to build a cross-compiler
first on another machine.  Keep in mind that this requires about 20MB free
disk space just to work on it.  You need a directory that takes up about 10MB,
which contains source for the gcc compiler to generate amiga code (the
cross-compiler).  Then, in another 10MB directory, you need the source
for the compiler that should run on the amiga, when compiled with the 
cross-compiler from the other directory.

Based on timing from a sun, I'd guess it might take 20-30 minutes to recompile
gcc on an amiga (provided you had a gcc cross compiler running on the amiga).
One of the things that makes development slow is that all the modules
"depend" on the configuration files, so whenever you fix a tiny bug in one
of them, you have to recompile everything.  So, to make 10 changes, it
takes all day.

Fortunately, my amiga is on an ethernet with a mainframe, which can recompile
the whole gcc in about 3 minutes.  I found it reasonable to make a 
gnu cross-compiler generate amiga-style assembler and then invoke a68k
to create amiga-style .o files.  Then I pop back into another window
on the amiga to run blink.  Boy, I wish I had the source to blink so
I could run the whole thing on the mainframe.

Anyhow, it's been a real pain getting a68k to understand gcc output.  I've
had to make considerable changes to both.  I just got a new version of
a68k (2.42) and gcc (1.35), so I'll try to move my changes to these new
versions.  I can compile some trivially simple test cases, but haven't
been able to compile gcc itself with the cross-compiler.

I'll work on it for a couple more weeks, and post whatever I have then.

Steve

-- 

        Steve Schoettler
        shs@uts.amdahl.com
        {sun,decwrl,pyramid,ames,uunet}!amdahl!shs
        Amdahl Corp., M/S 213, 1250 E. Arques Ave, Sunnyvale, CA 94088