From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2
Date: Thu, 08 Sep 2011 20:30:00 -0000 [thread overview]
Message-ID: <20110908202949.GA32219@ednor.casa.cgf.cx> (raw)
In-Reply-To: <CAPw2spgdvGCJSBvcigsKhqoUnOinG2UGmN2jVg3qQxRvZ2uxjA@mail.gmail.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
next prev parent reply other threads:[~2011-09-08 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 4:02 Dave Korn
2011-09-06 19:45 ` Bernd Prager
2011-09-06 21:28 ` Yaakov (Cygwin/X)
2011-09-08 16:34 ` Bernd Prager
2011-09-09 4:23 ` Dave Korn
2011-09-09 15:38 ` Dave Korn
2011-09-11 7:50 ` Bernd Prager
2011-09-11 16:29 ` Bernd Prager
2011-09-08 5:32 ` Frédéric Bron
2011-09-08 12:19 ` Ryan Johnson
2011-09-08 20:18 ` Frédéric Bron
2011-09-08 20:30 ` Christopher Faylor [this message]
2011-09-08 22:44 ` Frédéric Bron
2011-09-08 23:34 ` Ryan Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110908202949.GA32219@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).