Message-ID: <001601c93b31$a961b940$4001a8c0@mycomputer>
From: "John Emmas" <johne53@tiscali.co.uk>
To: <cygwin@cygwin.com>
References: <000201c93ac7$38265930$4001a8c0@mycomputer> <490A30C8.5000107@sh.cvut.cz>
Subject: Re: cygwin g++ strictness
Date: Fri, 31 Oct 2008 08:21:23 -0000
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="Windows-1252"; 	reply-type=original
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

----- Original Message ----- 
From: "Larry Hall (Cygwin)"
Sent: 30 October 2008 22:23
Subject: Re: cygwin g++ strictness
>
> This is gcc/g++ question, not a Cygwin one.  Please find an appropriate
> forum to ask this question if you can't find it in the available
> documentation.
>

----- Original Message ----- 
From: "Vaclav Haisman"
Sent: 30 October 2008 22:10
Subject: Re: cygwin g++ strictness
>
> I think the problem is between keyboard and chair. GCC, no matter how
> ancient version, just does not do that.
>
Regardless of your ascerbic comments, adding the compiler flag -fpermissive
seems to have solved the problem.   Cygwin's version of gcc seems to be 3.4
on my system whereas my Linux box is running 4.4.  Maybe this is something
that got relaxed between the two of them?  Whatever the explanation, the 
exact same code compiles fine under Linux/gcc4.4 without needing that flag.
Maybe it wouldn't have done under Linux/gcc3.4?

John


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/