🚀 go-pugleaf

  OK, here's a capsule summary of what's happened so far.  Anyone 
who wants to comment on any of this, feel free.

  All of these builds are happening under SCO ODT 3.0 on a 486DX2/50.
So far, I've built gzip-1.2.4, fileutils-3.9, gas-2.2, bison-1.22,
flex-2.4.5, binutils-2.3 (having had to hack the source a bit),
gcc-2.5.7, make-3.69, diffutils-2.6, textutils-1.9, shellutils-1.9.2
(without the "su" command), bash-1.13.5, perl-4.036, tar-1.11.2
cpio-2.3, and uemacs311 (microEmacs, not an FSF product, but it seemed
easy to do, so I did it).  More on gcc-2.5.7 later.

  The eventual repository for this stuff is digibd.com.  In a few
days, I will copy this stuff into digibd.com:/incoming/scognu, from
where it is copied into digibd.com:/pub/sco-ports/gnu -- that's where
you should be getting it from.  There's some stuff there now, but
nowhere near all of it, so you may as well wait a bit for the rest.
(I think you can get as, ld, make and a few other things right now.)

  Each package above comes in its own gzipped tar file, with all
appropriate parts, including info and man files.  In addition, there
will be numerous README files for each package that I think needs
some extra commentary.  Also, there will be a README-build file that
shows how I built all of this from scratch, for the keeners among you.

gcc-2.5.7
---------

  One of the main goals is to build a standalone development system,
supporting both C and C++, even Objective C for the lunatic fringe :-).
So far, this has been elusive.  Here's what's happened so far.

  I built gcc using both gnu as and ld, only going as far as stage1
before installing.  Not only does this take less time, but if you
actually make stage2, trying to build "objc-runtime" later fails.
Go figure.  The error message is "Don't know how to make hash.o."
Strange, but I only get this error from stage2, not if I stop at
stage1 and build objc-runtime there.  Any clues?  Weird.

  The second problem I tracked down is a failure to build cc1plus.
I get "Virtual memory exhausted!".  My first thought was to shut off
stuff I didn't need (NFS, TCP/IP, ...) and try the make again.
This make completed, but unknown to me, it didn't build cc1plus
properly.  The first failure left around a damaged, non-runnable
cc1plus, which got installed.  This became apparent later when I
tried to build libg++-2.5.2.  To get around this, I stole cc1plus
from another pre-built distribution and installed it, but I would
prefer to have my build succeed cleanly.  Any hints on now to avoid
running out of virtual memory?  Nothing I do seems to help.

  Finally, I can distribute the build of gcc-2.5.7 I have so far so
that people who have the SCO dev sys can use it on top of their
runtime libs.  However, I cannot distribute the "fixed" header files
as they are SCO proprietary.  Several people have pointed out that
I can simply distribute the fixinc.sco script which patches the SCO
header files.  To save me trying to figure out what has to be included,
could someone please tell me EXACTLY what I have to include with the
gcc-2.5.7 prebuild for this to work?

  Have I covered everything?  I'm still fighting with glibc-1.06
and libg++-2.5.2.  More on this later.

R. Day
Calgary, Alberta