RE: tux+php

["Valkanas Nikos" <nbal hq otenet gr>]

> -----Original Message-----
> From: J Sloan [mailto:joe@tmsusa.com]
> Sent: Saturday, March 02, 2002 8:55 PM
> To: tux-list@redhat.com
> Subject: Re: tux+php
> 
> 
> Valkanas Nikos wrote:
> 
> >Reagardless, I have found several products claiming that 
> gcc-2.96 and higher (gcc-3.xx) produce broken code. They 
> suggest downgrading to gcc-2.92 till gcc-2.94. I myself 
> downgraded to gcc-2.93 (requires downgrading cpp to 2.93 and 
> libstd++ to the same level). I will try to implement the 
> mime_types php support using this compiler. If 2.96 is OK, 
> then my build should work the same with the 2.96 compiler.
> >
> gcc-2.96 is one of the most solid compilers I've
> ever used.
> 
> The 2.96 that ship with RH 7.x where x >0
> is fine - there was a problem in the gcc 2.96
> that originally shipped with RH 7.0 back in
> the year 2000. Some people are obsessed with
> that original gcc-2.96 bug, and can't keep from
> ranting about it, despite the fact that it's been
> fixed for a long long time now.
> 
> Joe
> 

Hmmm... There have been runtime problems with some products. I understand that there have been some heated debates (and flames!) about it. Check the official gcc response: http://gcc.gnu.org/gcc-2.96.html. 2.96 is not an official gcc release and is not maintained by gcc.

Mind you I am not picking any sides. It is bad enough when you are a developer to chase down bugs, let alone dealing with a less than sure compiler.

Nikos