X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4E68AA10.4070205@cs.utoronto.ca> References: <4E68AA10.4070205@cs.utoronto.ca> From: =?ISO-8859-1?Q?Fr=E9d=E9ric_Bron?= Date: Thu, 8 Sep 2011 22:17:57 +0200 Message-ID: Subject: Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2 To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p88KIx34005262 > In my experience, these sorts of errors arise when there really is something > wrong with the code, usually involving sizes of integers (e.g. 'long' in > struct's definition and 'int' in another, on a 64-bit machine). However, the > linker is poorly-equipped to detect such errors unless the resulting objects > have different sizes. > > So, while I wouldn't rule out miscompilation, I would first check for > silently conflicting definitions in different compilation units. Does the linker message gives any hint on where to look? > BTW, a STC would have been extremely helpful here -- all we can do is > speculate without it Could you give more details. I cannot find on the net what you mean by "a STC". Thanks, Frédéric -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple