delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT 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 <cgf-use-the-mailinglist-please AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2 |
Message-ID: | <20110908202949.GA32219@ednor.casa.cgf.cx> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <announce DOT 4E60524C DOT 2000401 AT gmail DOT com> <CAPw2spgAfEF-vLrWeoFTA28Xtt5WcvYS+mVqq9RUqi4CYk84rQ AT mail DOT gmail DOT com> <4E68AA10 DOT 4070205 AT cs DOT utoronto DOT ca> <CAPw2spgdvGCJSBvcigsKhqoUnOinG2UGmN2jVg3qQxRvZ2uxjA AT mail DOT gmail DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <CAPw2spgdvGCJSBvcigsKhqoUnOinG2UGmN2jVg3qQxRvZ2uxjA@mail.gmail.com> |
User-Agent: | Mutt/1.5.20 (2009-06-14) |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 |
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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |