From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32585 invoked by alias); 15 Jun 2012 21:30:06 -0000 Received: (qmail 32555 invoked by uid 22791); 15 Jun 2012 21:30:04 -0000 X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 15 Jun 2012 21:29:51 +0000 Received: by wibhr14 with SMTP id hr14so809672wib.2 for ; Fri, 15 Jun 2012 14:29:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.194.95 with SMTP id l73mr3621303wen.206.1339795787177; Fri, 15 Jun 2012 14:29:47 -0700 (PDT) Received: by 10.216.153.41 with HTTP; Fri, 15 Jun 2012 14:29:47 -0700 (PDT) In-Reply-To: <4FD22835.1000301@cs.utoronto.ca> References: <4FD22835.1000301@cs.utoronto.ca> Date: Fri, 15 Jun 2012 21:30:00 -0000 Message-ID: Subject: Re: i686-pc-mingw32-gcc 4.5.2 and static linking libstdc++-6? From: Dennis Isenhour To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 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: 2012-06/txt/msg00304.txt.bz2 Just to close the loop on this for anyone who might be encountering a similar issue or situation in the future, with the simple test example info Ryan Johnson provided me in the previous response, I was able to eventually narrow down my problem to a makefile complexity. The makefile was setting the link flag '-lstdc++' at a point in the build process AFTER it had already specified the -static-libstdc++ option, thus overriding it. I'm not exactly sure where/how it was switched to make the -lstdc++ be interpeted as dynamic, but regardless it was obviously not only redundant but overriding the earlier specified -static option. And while I'm being 100% thorough I should probably just re-state more clearly that the other *separate* problem I had (which was resolved in an earlier post), the makefile had actually been mixing g++ for some compiles and gcc for others, but using gcc for producing the end executable, so i switched it to just make use of g++ which obviously resolved the "unrecognized option" issue I had mentioned I had been seeing before. Thanks very much for all the help, especially to Ryan. -Dennis -- 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