🚀 go-pugleaf

 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.  i
would just like to post a couple of comments as a small 
contribution to this venerable and noble effort.
 
1.)  gnu's part of the free software foundation ( or maybe the
other way around? ), which is really attractive to those of us
with home unix boxes and not lots of cash.  it is really a 
pity that most ports to such unix make reference to the 
exorbitantly priced flavors ( e.g. sco unix, interactive/bell unix )
which flavors are almost as expensive as my box!!.  maybe we really 
ought to reward those folks who are perhaps pricing their 
products more in the direction of free ( i.e. cheap ) like
the everex ESIX expression of System V.. 

2.) the notes accompanying the binutils which discuss building a
COFF-ENCAPSULATED system V gnu development system ( i.e. file
README-ENCAP in binutils ) are simply not correct.  the instructions
claim that one ought to first build gcc with the i386-sysv-gas 
configuration, and then to build the gas assembler and gnu binutils.
not so!  the i386-sysv-gas requires, by assumption, gas and gnu ld
to be available for the building process, so this method cannot work.
 
have gotten gcc, gas, and gnu ld to compile individually, so i now
hope to use the i386-sysv-gas option.  ... if only i could figure
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=

jeff p woodward
woodward@uicbert.eecs.uic.edu