From: Greg Chicares <gchicares@sbcglobal.net>
To: cygwin@cygwin.com
Subject: Re: i686-pc-mingw32-gcc 4.5.2 and static linking libstdc++-6?
Date: Fri, 01 Jun 2012 22:41:00 -0000 [thread overview]
Message-ID: <4FC944F5.6020402@sbcglobal.net> (raw)
In-Reply-To: <CALAJ8nR96ag_LRkQUJerzBQkXgf9YCV+P8eDid2z7FpHW3a+YQ@mail.gmail.com>
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: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-06-01 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 17:29 Dennis Isenhour
2012-06-01 19:34 ` Earnie Boyd
2012-06-05 21:28 ` Linda Walsh
2012-06-01 22:41 ` Greg Chicares [this message]
2012-06-08 14:55 ` Dennis Isenhour
2012-06-08 16:28 ` Ryan Johnson
2012-06-15 21:30 ` Dennis Isenhour
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=4FC944F5.6020402@sbcglobal.net \
--to=gchicares@sbcglobal.net \
--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).