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
On 2012-06-01 22:40, Greg Chicares wrote:
What if you use i686-pc-mingw32-g++ instead of i686-pc-mingw32-gcc?
I've tried that (so i'm no longer receiving the unrecognized option
warning message), but I must still be doing something wrong as I'm
still having the same problem. It doesn't appear to
On 08/06/2012 10:55 AM, Dennis Isenhour wrote:
On 2012-06-01 22:40, Greg Chicares wrote:
What if you use i686-pc-mingw32-g++ instead of i686-pc-mingw32-gcc?
I've tried that (so i'm no longer receiving the unrecognized option
warning message), but I must still be doing something wrong as I'm
Had to look up that acronym, and saw this one right above it:
TMTOWTDI
Oh the irony ;-)
Earnie Boyd wrote:
On Fri, Jun 1, 2012 at 1:29 PM, Dennis Isenhour wrote:
Can someone tell me, is static linking of libstdc++(-6 ?) not
currently supported in cygwin using the mingw compiler?
Can someone tell me, is static linking of libstdc++(-6 ?) not
currently supported in cygwin using the mingw compiler?
On Thu, May 31, 2012 at 1:55 PM, Dennis Isenhour
dennis.isenh...@gmail.com wrote:
Please excuse me if this isn’t the correct place for this question or
if I’ve misunderstood
On Fri, Jun 1, 2012 at 1:29 PM, Dennis Isenhour wrote:
Can someone tell me, is static linking of libstdc++(-6 ?) not
currently supported in cygwin using the mingw compiler?
http://cygwin.com/acronyms/#TOFU
IDK, but maybe with -static-libstdc++ it would work.
--
Earnie
--
On 2012-06-01 17:29Z, Dennis Isenhour wrote:
i686-pc-mingw32-gcc: unrecognized option '-static-libstdc++'
What if you use i686-pc-mingw32-g++ instead of i686-pc-mingw32-gcc?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
7 matches
Mail list logo
