🚀 go-pugleaf

I wrote:

: gcc-2.5.7
: ---------

:   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.

OK, I beat this.  I just removed the "-g" CFLAGS option from the make
involving stage1.

  $ make CC="stage1/xgcc -Bstage1/" CFLAGS="-O"    (No "-g" flag anymore.)

  Was this a bad decision?  It solved the problem, so it can't be
all bad.  Comments?

rday

:   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