public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lts-rudolph at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53304] use of std::future results to relocation error with symbol _ZTINSt13__future_base19_Async_state_commonE
Date: Thu, 10 May 2012 14:57:00 -0000 [thread overview]
Message-ID: <bug-53304-4-IKR1LIWjRe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53304-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53304
Klaus Rudolph <lts-rudolph at gmx dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #2 from Klaus Rudolph <lts-rudolph at gmx dot de> 2012-05-10 14:57:07 UTC ---
> You need to tell the dynamic linker how to find the 4.7 libs
You are right. ld.so.config points to older build of pre-release version of gcc
4.7. Status could be changed to invalid.
next prev parent reply other threads:[~2012-05-10 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 9:12 [Bug c++/53304] New: " lts-rudolph at gmx dot de
2012-05-10 14:57 ` lts-rudolph at gmx dot de [this message]
2012-05-10 14:57 ` [Bug c++/53304] " redi at gcc dot gnu.org
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=bug-53304-4-IKR1LIWjRe@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).