public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/66030] [5.1.0] std::codecvt_byname missing from libstdc++ DLL
Date: Mon, 01 Jun 2015 16:30:00 -0000	[thread overview]
Message-ID: <bug-66030-4-n0FAaCdDxp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66030-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66030

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Does this work?

--- a/libstdc++-v3/config/abi/pre/gnu.ver
+++ b/libstdc++-v3/config/abi/pre/gnu.ver
@@ -542,6 +542,9 @@ GLIBCXX_3.4 {
     # std::codecvt_byname
     _ZNSt14codecvt_bynameI[cw]c11__mbstate_tEC[12]EPKc[jmy];
     _ZNSt14codecvt_bynameI[cw]c11__mbstate_tED*;
+#if defined (_WIN32) && !defined (__CYGWIN__)
+    _ZNSt14codecvt_bynameI[cw]ciE[CD]*;
+#endif

     # std::collate
     _ZNSt7collateI[cw]*;

This won't affect any targets which use versioned symbols.


  parent reply	other threads:[~2015-06-01 16:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 23:34 [Bug libstdc++/66030] New: " sailer at sailer dot dynip.lugs.ch
2015-05-05 23:35 ` [Bug libstdc++/66030] " sailer at sailer dot dynip.lugs.ch
2015-05-26 13:49 ` hamzaalloush at live dot com
2015-05-27 15:08 ` redi at gcc dot gnu.org
2015-06-01 16:02 ` jroivas at iki dot fi
2015-06-01 16:21 ` redi at gcc dot gnu.org
2015-06-01 16:30 ` redi at gcc dot gnu.org [this message]
2015-06-01 17:49 ` jroivas at iki dot fi
2015-06-01 18:22 ` jroivas at iki dot fi
2015-06-01 22:49 ` redi at gcc dot gnu.org
2015-06-05 16:56 ` jroivas at iki dot fi
2015-06-06  8:49 ` ktietz at gcc dot gnu.org
2015-06-06 12:10 ` redi at gcc dot gnu.org
2015-06-08 15:13 ` redi at gcc dot gnu.org
2015-06-09  4:42 ` jroivas at iki dot fi
2015-06-15 12:31 ` redi at gcc dot gnu.org
2015-06-15 12:32 ` redi at gcc dot gnu.org
2015-07-04  0:50 ` hamzaalloush at live dot com

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-66030-4-n0FAaCdDxp@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).