X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
X-Trace: 97087348/mk-filter-4.mail.uk.tiscali.com/B2C/$b2c-THROTTLED-DYNAMIC/b2c-CUSTOMER-DYNAMIC-IP/79.66.2.206/None/johne53 AT tiscali DOT co DOT uk
X-SBRS: None
X-RemoteIP: 79.66.2.206
X-IP-MAIL-FROM: johne53 AT tiscali DOT co DOT uk
X-MUA: Microsoft Outlook Express 6.00.2900.2180Produced By Microsoft MimeOLE  V6.00.2900.2180
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqwEAApdCklPQgLO/2dsb2JhbACEG1XIAINR
X-IronPort-AV: E=Sophos;i="4.33,521,1220223600";     d="scan'208";a="97087348"
Message-ID: <001601c93b31$a961b940$4001a8c0@mycomputer>
From: "John Emmas" <johne53 AT tiscali DOT co DOT uk>
To: <cygwin AT cygwin DOT com>
References: <000201c93ac7$38265930$4001a8c0 AT mycomputer> <490A30C8 DOT 5000107 AT sh DOT cvut DOT 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
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT 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/