X-Recipient:	archive-cygwin AT delorie DOT com
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
MIME-Version:	1.0
In-Reply-To:	<4FD22835.1000301@cs.utoronto.ca>
References:	<CALAJ8nR96ag_LRkQUJerzBQkXgf9YCV+P8eDid2z7FpHW3a+YQ AT mail DOT gmail DOT com> <CALAJ8nTQwksEWCeG-pF-2v_XcHPOsMWj=Gqzf+6W-COVnS0A_Q AT mail DOT gmail DOT com> <4FD22835 DOT 1000301 AT cs DOT utoronto DOT ca>
Date:	Fri, 15 Jun 2012 17:29:47 -0400
Message-ID:	<CALAJ8nSaoZCLL1F0FSvbd2_f3zGbE7RibP3_MjFRscv-CWx+2g@mail.gmail.com>
Subject:	Re: i686-pc-mingw32-gcc 4.5.2 and static linking libstdc++-6?
From:	Dennis Isenhour <dennis DOT isenhour AT gmail DOT com>
To:	cygwin AT cygwin DOT com
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

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

- Raw text -