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++/97729] Link failure due to basic_stringbuf and others when building DLL on MinGW Date: Thu, 05 Nov 2020 13:48:39 +0000 [thread overview] Message-ID: <bug-97729-4-ZnbBYMrPV1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97729-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97729 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2020-11-05 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Created attachment 49505 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49505&action=edit Instantiate and export missing constructor I can't reproduce this with a x86_64-w64-mingw32 cross-compiler built on linux, nor with a native linux compiler. But this patch should fix it, could you test it please?
next prev parent reply other threads:[~2020-11-05 13:48 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-05 12:51 [Bug libstdc++/97729] New: " markus.boeck02 at gmail dot com 2020-11-05 13:48 ` redi at gcc dot gnu.org [this message] 2020-11-05 13:49 ` [Bug libstdc++/97729] [11 Regression] " redi at gcc dot gnu.org 2020-11-05 14:00 ` markus.boeck02 at gmail dot com 2020-11-05 14:05 ` redi at gcc dot gnu.org 2020-11-05 14:20 ` markus.boeck02 at gmail dot com 2020-11-05 14:37 ` redi at gcc dot gnu.org 2020-11-05 18:01 ` cvs-commit at gcc dot gnu.org 2020-11-05 18:01 ` cvs-commit at gcc dot gnu.org 2020-11-05 18:05 ` redi at gcc dot gnu.org 2020-11-05 18:05 ` redi at gcc dot gnu.org 2020-11-05 19:22 ` markus.boeck02 at gmail dot com 2020-11-05 19:32 ` redi at gcc dot gnu.org 2020-11-09 14:29 ` cvs-commit 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-97729-4-ZnbBYMrPV1@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: linkBe 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).