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:21:00 -0000 [thread overview]
Message-ID: <bug-66030-4-wbM6aX3ITl@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 #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jouni Roivas from comment #3)
> Created attachment 35668 [details]
> proposed patch
>
> This patch solves this problem for me. However I'm not sure if it covers all
> the cases.
This is wrong because it adds the symbols to a frozen symbol version, we need a
new symbol version.
What I don't understand is why the symbols are only missing now, when they've
never been correctly exported, even prior to GCC 5.
next prev parent reply other threads:[~2015-06-01 16:21 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 [this message]
2015-06-01 16:30 ` redi at gcc dot gnu.org
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-wbM6aX3ITl@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).