From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5250 invoked by alias); 8 Sep 2011 12:19:43 -0000 Received: (qmail 5236 invoked by uid 22791); 8 Sep 2011 12:19:40 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Received: from smtp0.epfl.ch (HELO smtp0.epfl.ch) (128.178.224.219) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Thu, 08 Sep 2011 12:19:19 +0000 Received: (qmail 31555 invoked by uid 107); 8 Sep 2011 12:19:15 -0000 Received: from sb-gw13.cs.toronto.edu (HELO discarded) (128.100.3.13) (authenticated) by smtp0.epfl.ch (AngelmatoPhylax SMTP proxy) with ESMTPA; Thu, 08 Sep 2011 14:19:16 +0200 Message-ID: <4E68AA10.4070205@cs.utoronto.ca> Date: Thu, 08 Sep 2011 12:19:00 -0000 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-09/txt/msg00058.txt.bz2 On 08/09/2011 1:32 AM, Frédéric Bron wrote: > I have recompiled the code I am working on with i686-pc-cygwin-g++ 4.5.3. > > I get many of the following messages from the linker: > /usr/lib/gcc/i686-pc-cygwin/4.5.3/../../../../i686-pc-cygwin/bin/ld: > gcc-release/obj/BTest/Test.o: warning: duplicate section > `.rdata$_ZTISs[typeinfo for std::basic_string std::char_traits, std::allocator >]' has different size > > I do not get this error cross-compiling the same code with > i686-pc-mingw32-g++ 4.5.2. > > Any chance that this comes from the new version? 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. At least one list discussion for another project reported a similar gcc-whines-mingw-silent issue, and the resulting mingw binary didn't run properly (which supports the silent conflict hypothesis). BTW, a STC would have been extremely helpful here -- all we can do is speculate without it Ryan -- 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