Message-ID: <00cf01c93b5e$e75ff540$4001a8c0@mycomputer>
From: "John Emmas" <johne53@tiscali.co.uk>
To: <cygwin@cygwin.com>
References: <000201c93ac7$38265930$4001a8c0@mycomputer> <490A30C8.5000107@sh.cvut.cz> <001601c93b31$a961b940$4001a8c0@mycomputer> <003e01c93b42$e92a17a0$4001a8c0@mycomputer> <490AE8A0.8090009@sh.cvut.cz> <001a01c93b4d$617de150$4001a8c0@mycomputer> <490AF1E3.3020308@sh.cvut.cz> <007401c93b56$ebcfa510$4001a8c0@mycomputer> <490B0084.1070803@sh.cvut.cz> <008a01c93b5a$9338d300$4001a8c0@mycomputer> <490B078B.9030007@byu.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
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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/