[1413] in Release_7.7_team
Re: Cygnus GCC
daemon@ATHENA.MIT.EDU (Thomas Bushnell, BSG)
Fri Jul 31 12:35:18 1998
Date: Fri, 31 Jul 1998 12:35:10 -0400
From: tb@MIT.EDU (Thomas Bushnell, BSG)
To: alexp@MIT.EDU
Cc: ghudson@MIT.EDU, alexp@MIT.EDU, release-team@MIT.EDU
In-Reply-To: Alex T Prengel's message of Fri, 31 Jul 1998 12:31:39 EDT
<199807311631.MAA07424@dit.mit.edu>
Date: Fri, 31 Jul 1998 12:31:39 EDT
From: Alex T Prengel <alexp@MIT.EDU>
>It's true, though, that the cygnus locker gcc will continue to cause a
>support burden as long as it sits there and fails to work.
I haven't heard this before and it seems to work for me. In what way
is it broken? I'm reluctant to delete cygnus unless there is a good
reason... People still use it. I have a README popup that explains
the situation and that the gnu locker will be the place for new
releases. Is there more to this than I am aware of?
Older versions of GCC will not work on Irix 6 because Irix added a
special built-in type to their compiler and they use it in their
header files. Newer GCC does work fine (because the misfeature was
copied into GCC) but older GCC doesn't know about it, and will fail on
Irix 6.
Thomas
