public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yucong Sun <sunyucong@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: C++11 program link failure under GCC 4.8.2-1
Date: Mon, 11 Nov 2013 23:38:00 -0000	[thread overview]
Message-ID: <CAJygYd2H7tyjE73=EK2hdo2ZPvWtziU8sUkbgbo5crBtP3JRHQ@mail.gmail.com> (raw)
In-Reply-To: <528159F8.2070307@gmail.com>

Yes, the sha1 matches.

sunyc@sunyc-wks /lib/gcc/i686-pc-cygwin/4.8.2
$ sha1sum.exe libstdc++.*
f4dfadfddade3aceaf4852cd5db31372ab7ef0d1 *libstdc++.a
963e2a697c3a1a7d036d975b07f4c408bbd1cb2d *libstdc++.dll.a

Also I couldn't find GLIB_xxx version number in libstdc++.a

sunyc@sunyc-wks /lib/gcc/i686-pc-cygwin/4.8.2
$ strings.exe libstdc++.a | grep GLIB
GLIBCXX_FORCE_NEW
GLIBCXX_FORCE_NEW
GLIBCXX_DEBUG_MESSAGE_LENGTH

Cheers.

On Mon, Nov 11, 2013 at 2:28 PM, JonY <10walls@gmail.com> wrote:
> On 11/12/2013 06:17, JonY wrote:
>> On 11/12/2013 05:17, Yucong Sun wrote:
>>> Hi,
>>>
>>> I'm trying to compile a program under cygwin with latest gcc 4.8.2,
>>> the program compiles fine, but link failed. I'm suspecting this has
>>> something todo with libstdc++ but I couldn't find any document on how
>>> to check libstdc++ version (cygwin setup claim it is version 4.8.2
>>> already).
>>>
>>
>> I'm not sure either, could you ask gcc-help instead?
>>
>>
>
> 963e2a697c3a1a7d036d975b07f4c408bbd1cb2d *libstdc++.dll.a
> f4dfadfddade3aceaf4852cd5db31372ab7ef0d1 *libstdc++.a
>
> Is your sha1sum matching mine for 4.8.2?
>
>

--
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

  reply	other threads:[~2013-11-11 23:38 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 [this message]
2013-11-12  2:34       ` Yucong Sun
2013-11-12  2:38         ` Yucong Sun
2013-11-12  9:46         ` JonY
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='CAJygYd2H7tyjE73=EK2hdo2ZPvWtziU8sUkbgbo5crBtP3JRHQ@mail.gmail.com' \
    --to=sunyucong@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).