🚀 go-pugleaf

woodward@uicbert.eecs.uic.edu (Jeff Woodward) writes:
>
>> have just gotten gcc 1.37 and am trying to bring it up on my
>>home box, a generic 386 clone running ESIX System V unix.
>>...
>>have gotten gcc, gas, and gnu ld to compile individually, so i now
>>hope to use the i386-sysv-gas option.
>>out why ld bites the big one on the system V crt0.o file, and how
>>i can fix this since gnu robotussin won't eat crt0.o either. =sigh=

I've been bringing up Gnu software on SCO Unix, which is actually an
inexpensive system if you don't buy the development system (~$600 for
the basics).  You need the development system to bootstrap gcc from
source code.

It all works well, but I'd like to make a suggestion that distribution
sites maintain FTP-able binaries of the bootstrap utilities (gcc, gas,
ld) for SCO Unix.  (This will duly deprive Microsoft of the ~$700 they
get for each copy of C and Codeview they eek out of SCO Unix users.)
"Free" versions of /usr/include and /usr/include/sys would also have to
be created and put in this release.

I've noticed a definite BSD bias in some of the Gnu software.  System V
still has cruftiness like the 14-character filename limit, which for
example the Makefile contained in the g++ release doesn't obey.  The
utilities work, but building them on sysV requires significant knowledge
of C coding, make, and obscure shell commands.

Gnu has actually come quite a long way recently.  I've managed to set up
a rather comfortable development environment without having to line the
pockets of Microsoft or SCO.  On my wish list:  network software...

-rich