public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/54872] New: [4.8 regression] abi_check FAILs on Solaris 10/11 Date: Tue, 09 Oct 2012 09:44:00 -0000 [thread overview] Message-ID: <bug-54872-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54872 Bug #: 54872 Summary: [4.8 regression] abi_check FAILs on Solaris 10/11 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: ro@gcc.gnu.org CC: bkoz@gcc.gnu.org Host: *-*-solaris2.1[01] Target: *-*-solaris2.1[01] Build: *-*-solaris2.1[01] abi_check currently FAILs on Solaris 10 and 11(both SPARC and x86, 32 and 64-bit), Solaris 9 is unaffected. On Solaris 10, I get 1 incompatible symbols 0 _ZNSt12system_errorC1ESt10error_codeRKSs std::system_error::system_error(std::error_code, std::string const&) version status: incompatible GLIBCXX_3.4.11 type: function status: added On Solaris 11, I get: 2 incompatible symbols 0 _ZNSt12system_errorC2ESt10error_codeRKSs std::system_error::system_error(std::error_code, std::string const&) version status: incompatible GLIBCXX_3.4.11 type: function status: added 1 _ZNSt12system_errorC1ESt10error_codeRKSs std::system_error::system_error(std::error_code, std::string const&) version status: incompatible GLIBCXX_3.4.11 type: function status: added Rainer
next reply other threads:[~2012-10-09 9:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-09 9:44 ro at gcc dot gnu.org [this message] 2012-10-09 9:44 ` [Bug libstdc++/54872] " ro at gcc dot gnu.org 2012-10-11 8:39 ` ro at gcc dot gnu.org 2012-10-11 8:41 ` ro 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-54872-4@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).