public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/83077] sso-string @ gnu-versioned-namespace.
Date: Wed, 06 Sep 2023 06:56:58 +0000 [thread overview]
Message-ID: <bug-83077-4-O5MB6GYS8U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-83077-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83077
--- Comment #11 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to François Dumont from comment #10)
> This is because you are facing the PR65762 issue. I just attached a path
> proposal to it that you need to apply too to be able to run your test.
> You'll be even able to simply use --disable-libstdcxx-dual-abi cause I made
> cxx11 abi the default in this case.
Yes, with the second patch applied, that works for me also.
Does gnu-versioned-namespace work for you with these two patches applied?
(I have a patch to enable versioned namespace on Darwin, which is very similar
to the GNU one, but it no longer builds)..
next prev parent reply other threads:[~2023-09-06 6:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-83077-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` jakub at gcc dot gnu.org
2020-03-12 12:59 ` redi at gcc dot gnu.org
2020-10-30 21:00 ` redi at gcc dot gnu.org
2021-02-28 14:42 ` fdumont at gcc dot gnu.org
2023-08-10 13:05 ` redi at gcc dot gnu.org
2023-09-01 13:42 ` iains at gcc dot gnu.org
2023-09-02 7:11 ` fdumont at gcc dot gnu.org
2023-09-02 9:23 ` iains at gcc dot gnu.org
2023-09-02 18:04 ` iains at gcc dot gnu.org
2023-09-03 12:22 ` fdumont at gcc dot gnu.org
2023-09-06 6:56 ` iains at gcc dot gnu.org [this message]
2023-09-06 7:21 ` iains at gcc dot gnu.org
2023-09-07 6:28 ` iains at gcc dot gnu.org
2023-09-07 17:04 ` fdumont at gcc dot gnu.org
2023-09-07 17:09 ` iains at gcc dot gnu.org
2023-09-07 17:10 ` iains at gcc dot gnu.org
2023-09-07 17:16 ` fdumont at gcc dot gnu.org
2023-09-07 17:20 ` iains at gcc dot gnu.org
2023-09-07 18:41 ` iains at gcc dot gnu.org
2023-09-23 19:35 ` fdumont 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-83077-4-O5MB6GYS8U@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).