X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org X-Yahoo-SMTP: jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o- Date: Thu, 8 Sep 2011 16:29:49 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2 Message-ID: <20110908202949.GA32219@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4E68AA10.4070205@cs.utoronto.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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 On Thu, Sep 08, 2011 at 10:17:57PM +0200, Fr?d?ric Bron wrote: >> 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". http://cygwin.com/acronyms/#STC -- 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