> I'd like to strongly encourage contributors to the list to avoid
> replying to e-mail which contain these disclaimers. They give the
> administrators of gcc.gnu.org a legal liability, since we do not
> follow the directions in the disclaimer. It's true that we would
> almost certainly win a cou
"Dave Korn" <[EMAIL PROTECTED]> writes:
> On 23 July 2007 19:13, Ian Lance Taylor wrote:
>
> > "Venkatesan Jeevanandam" <[EMAIL PROTECTED]> writes:
> >
> >> DISCLAIMER:
> >> This message (including attachment if any) is confidential and may be
> >> privileged.
>
> > Please do not include this
On 23 July 2007 19:13, Ian Lance Taylor wrote:
> "Venkatesan Jeevanandam" <[EMAIL PROTECTED]> writes:
>
>> DISCLAIMER:
>> This message (including attachment if any) is confidential and may be
>> privileged.
> Please do not include this sort of disclaimer in messages sent to
> mailing lists host
"Venkatesan Jeevanandam" <[EMAIL PROTECTED]> writes:
> DISCLAIMER:
> This message (including attachment if any) is confidential and may be
> privileged. Before opening attachments please check them for viruses and
> defects. MindTree Consulting Limited (MindTree) will not be responsible for
> a
On Fri, 2007-07-20 at 11:35 +0530, Venkatesan Jeevanandam wrote:
> I am getting the below error message while compiling, can u please help me.
> Is there any problem with gcc in backward compatibility?
There are no guarantees about compiling old GCC releases with a more
modern version of GCC. A
Hi all,
I am trying to install gcc 3.2 in a Linux machine (x86, Fedora core 5), it
already have gcc 4.1.0 installed. (i.e. I am compiling with gcc 4.1.0)
I am getting the below error message while compiling, can u please help me.
Is there any problem with gcc in backward compatibility?
Thanks in
