🚀 go-pugleaf

It seems like every time I go to a new (for me) architecture, this happens
once, and then I'm never able to duplicate it again.  If this were the first
time I'd ever built gcc, I'd say it was me.  But I've been building gcc,
off and on, for over four years now, usually with success.

Using the 2.3.3-solaris binaries from prep, I first did fixed my includes,
and then I built gcc-2.3.3.  I had to go to (let me make sure I say this 
correctly, I don't need another lecture about what the stages are :-)) 
stage 4???  to get matching .o files.  Where:

    stage1 == 'make ...'; 
    stage2 == 'make stage1; make...'
    stage3 == 'make stage2; make...' 
    stage4 == 'make stage3; make...'

(Well, even if I got it wrong, you'll get the idea.)

Anyway, to reitterate:
    stage1 == 'make ...'; 
    stage2 == 'make stage1; make...'
    stage3 == 'make stage2; make...' 

'make compare' failed, so I went on to:
    stage 4 == 'make stage3; make...'
where 'make compare3' passed.

Like I said, if this were the first time that I had to go to stage4 to get 
the compare to pass, I'd say it's me, but...  (Well, maybe it is me :-))

Anyway, do you suppose it's safe for me to use the binaries I got from
stage4?

Thanks.

-- 

Kaleb Keithley                                kaleb@devvax.jpl.nasa.gov