On Mon, Aug 19, 2002 at 01:04:55PM -0700, Terry Lambert wrote: > > Blah Terry, TOTALLY 110% INCORRECT. The situation was the same as our > > FreeBSD 3.x users that still post PR's against RELENG_3 and want us to > > fix things. Even where there was complete patches against 2.94.3 > > available; the issue for the GCC people was one of not willing to spend > > the effort to re-test on all platforms. Same reason we don't upgrade > > RELENG_3 to the latest openssl (or any other lib) -- who knows what else > > would break that depended on version that is there now. > > I thought that this was true for the LD, but not true for the > GCC. I think this is a different problem here, since this > was a specific reference to GCC 2.95.
It is more true for GCC than anything I maintain(ed) in src/contrib/ > > > The inability to get patches into 2.95 is totally unrelated > > > to the fact that it was an older GCC, and completely related > > > to the fact that the patches were not submitted in accordance > > > with the GCC maintainer's guidelines, > > > > WRONG, WRONG, WRONG, WRONG !!! > > It *was* an older GCC?!? Now I'm confused. We *are* talking > about the a.out shared library support, right? Nope. We are talking about various exception and code generation bugs. ELF format and sjlj method. Very mainstream things for FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
