Re: gcc 2.8.1
Subject: Re: gcc 2.8.1
Date: Wed, Dec 02, 1998 at 09:50:25PM +0100
In reply to:J.H.M. Dassen Ray"
Quoting J.H.M. Dassen Ray"(firstname.lastname@example.org):
> On Wed, Dec 02, 1998 at 04:39:33 -0500, email@example.com wrote:
> > Quoting J.H.M. Dassen Ray"(firstname.lastname@example.org):
> [regarding gcc 2.8.1]
> > > Why? We have EGCS.
> > Yep, and slink is screwed up because of it.
> Congratulations on succeeding to raise my blood pressure.
> The problems we have in slink currently are NOT caused by EGCS. They
> resulted from libc6 being compiled with the maintainers local
> /usr/local/bin/cc rather than /usr/bin/gcc. This introduced symbols in libc6
> that shouldn't have been there. The problem cascaded into libraries compiled
> on systems that had this broken libc installed. Two of these were
> libstdc++2.8 and libstdc++2.9.
> It's not a fault of mine or of the other EGCS maintainers that the libc6
> maintainer choose to repair this problem in a way that broke just about
> every system that tracked "frozen".
> Tevens ben ik van mening dat Nederland overdekt dient te worden.
Woops, sorry. I had got the impression from all the postings that
egcs was what had caused it. Now that we have the stright scoop That
it _isn't/wasn't_ egcs, we can quit guessing!
Thanks for the information. Hope your blood pressure settles down.
> Unsubscribe? mail -s unsubscribe email@example.com < /dev/null
To the systems programmer, users and applications serve only to provide
a test load.
Wayne T. Topa <firstname.lastname@example.org>