X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-Trace: 97468311/mk-filter-3.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: AqwEADOpCklPQgLO/2dsb2JhbACEG1XISINR X-IronPort-AV: E=Sophos;i="4.33,522,1220223600"; d="scan'208";a="97468311" Message-ID: <00cf01c93b5e$e75ff540$4001a8c0@mycomputer> From: "John Emmas" To: References: <000201c93ac7$38265930$4001a8c0 AT mycomputer> <490A30C8 DOT 5000107 AT sh DOT cvut DOT cz> <001601c93b31$a961b940$4001a8c0 AT mycomputer> <003e01c93b42$e92a17a0$4001a8c0 AT mycomputer> <490AE8A0 DOT 8090009 AT sh DOT cvut DOT cz> <001a01c93b4d$617de150$4001a8c0 AT mycomputer> <490AF1E3 DOT 3020308 AT sh DOT cvut DOT cz> <007401c93b56$ebcfa510$4001a8c0 AT mycomputer> <490B0084 DOT 1070803 AT sh DOT cvut DOT cz> <008a01c93b5a$9338d300$4001a8c0 AT mycomputer> <490B078B DOT 9030007 AT byu DOT net> Subject: Re: cygwin g++ strictness Date: Fri, 31 Oct 2008 13:45:14 -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: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Thanks for everyone's help with this. I'm grateful for how quickly we tracked it down. I think I mentioned earlier that this is someone else's code and would involve me in changing dozens (if not hundreds) of modules. Casting seemed like the best workaround but as I've just found out from Dave, that isn't a safe solution for references. ----- Original Message ----- From: "Eric Blake" Sent: 31 October 2008 13:26 Subject: Re: cygwin g++ strictness > > On the other hand, gcc 4 may already be causing ABI changes, so maybe this > would be appropriate as part of the switch to gcc 4 and cygwin 1.7.0? > That's a good suggestion and will hopefully get some consideration. In the meantime this looks like being quite a time-consuming problem to solve.... :-( Cheers, 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/