From: JonY <10walls@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: C++11 program link failure under GCC 4.8.2-1
Date: Tue, 12 Nov 2013 09:46:00 -0000 [thread overview]
Message-ID: <5281F8D4.4090809@gmail.com> (raw)
In-Reply-To: <CAJygYd2UqXD3e-iguMUB1FUNDmCVmC5D7b1=zHqMVs1kJ8-+qw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
On 11/12/2013 10:33, Yucong Sun wrote:
> I've tried on both 32bit and 64bit clean cygwin install, the result is
> same. Something is wrong with cygwin's gcc.
>
> my configure script by default uses g++ --std=c++11, this still have
> problem of " no snprintf " , after I replace all snprintf() with
> sprintf() , I've met the same linkage problem again.
>
Something else is very wrong.
> g++ --std=gnu++0x "fixes" the snprintf problem, but it still have same
> linkage problem.
>
Please make a minimalist case, I've tried some basic C++11 features but
I don't get such errors.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]
next prev parent reply other threads:[~2013-11-12 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 21:17 Yucong Sun
[not found] ` <52815780.2010006@gmail.com>
2013-11-11 22:28 ` JonY
2013-11-11 23:38 ` Yucong Sun
2013-11-12 2:34 ` Yucong Sun
2013-11-12 2:38 ` Yucong Sun
2013-11-12 9:46 ` JonY [this message]
2013-11-12 18:35 ` Yucong Sun
2013-11-12 22:30 ` JonY
2013-11-12 23:38 ` Ryan Johnson
2013-11-12 23:51 ` Yucong Sun
2013-11-13 9:15 ` Corinna Vinschen
2013-11-13 14:01 ` Christopher Faylor
2013-11-13 15:19 ` Corinna Vinschen
2013-11-13 15:51 ` Christopher Faylor
2014-03-12 21:05 ` zosrothko
2013-11-12 9:44 ` JonY
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=5281F8D4.4090809@gmail.com \
--to=10walls@gmail.com \
--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).