🚀 go-pugleaf

	I have just installed the GNU GCC (v 2.4.5) and LIBG++ (v2.4)
tools, respectively, on a SunOS 4 platform.  The native stuff
works OK (it has passed a "Hello, Richard" basic sanity check for
both C and C++ files).

	Hurrah.  That was just the warmup exercise.

	Now, my MAIN quest is to (on the same host machine), generate a
cross-development environment for an embedded 68020 product.
This embedded 68020 product is actually quite capable (i.e., if
necessary, it can perform its own link, location, and other
ROMing operations - in other words, it has a disk and even runs
UNIX, albeit an older version): we just want to cross-compile
(including cross-assemble), and if possible, cross-link, on the
SUN, for performance and logistics reasons (there are many SUN
terminals and engineers, and very few embedded prototypes).

	The directions for generating a cross-compiler call for
bringing into existence a "substitute" libgcc1.a.  I'm certainly
prepared to do this, and have in fact re-written compiler helper
functions before, but I can't help but suspect that a
SPARC->MC680x0 cross implementation of GCC hasn't been done before,
and may in fact be quite a common cross combination.

	If I am correct, and you have done this, and your memory of it
isn't too painful, please contact me (jew@teleos.com) and share the
experience.

P.S. Already got the cross GAS (2.1) working on the SUN for MC680x0.