🚀 go-pugleaf

    I understand, but I don't quite agree.  There seems to be little
    appreciation of just how many 3B2 systems are "gathering dust" in
    various places, for want of some decent software.  GNU offers the
    promise, but those writing GNU software are into Suns, SGIs, and other
    "high end" machines.  

Actually, we never port our software to any machine except the ones we
want to run it on.  We always leave porting up to the users.

When a user does a port to a particular machine, whether we are
willing to support the changes depends on their cost in complexity.
Each alternate pathway makes it harder to understand the consequences
of a subsequent change.  This slows down maintenance, which takes time
away from development of new software.

Since our main goal is to produce a single complete operating system,
supporting its components on other systems is secondary at best.  We
can't afford to support all of them.

    I have received source (1.29) for GCC with 3B2 machine description files
    and am trying to compile it on a 3B2/300 under SysV Release 3.0.

This is a port I never received.  If it can be made to work in the
current version of GCC, and if its author can sign the appropriate
legal papers, then I can think about putting it in.