public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "htl10 at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/54448] New: many failures with /sbin/loader: Error: libstdc++.so.6: symbol "__pthread_mutex_init" unresolved Date: Sat, 01 Sep 2012 08:58:00 -0000 [thread overview] Message-ID: <bug-54448-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54448 Bug #: 54448 Summary: many failures with /sbin/loader: Error: libstdc++.so.6: symbol "__pthread_mutex_init" unresolved Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: htl10@users.sourceforge.net Am running 4.7.1 testsuite on alphaev68-dec-osf5.1a, and seeing a lot of 237556:./what-1.exe: /sbin/loader: Error: libstdc++.so.6: symbol "__pthread_mutex_init" unresolved 237556:./what-1.exe: /sbin/loader: Fatal Error: Load of "./what-1.exe" failed: Unresolved symbol name FAIL: 27_io/ios_base/failure/what-1.cc execution test about __pthread_mutex_init being unresolved. The previous testsuite result I summitted (http://gcc.gnu.org/ml/gcc-testresults/2011-08/msg00587.html) also seems to have a lot of unexpected failures for 4.6.1: === libstdc++ Summary === # of expected passes 4091 # of unexpected failures 2312 # of expected failures 80 # of unsupported tests 747 === g++ tests === I'll write again when 4.7.1. finishes.
next reply other threads:[~2012-09-01 8:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-01 8:58 htl10 at users dot sourceforge.net [this message] 2012-09-02 17:50 ` [Bug libstdc++/54448] " htl10 at users dot sourceforge.net 2012-09-25 4:41 ` htl10 at users dot sourceforge.net 2012-09-28 15:00 ` paolo.carlini at oracle dot com 2012-09-28 15:40 ` redi at gcc dot gnu.org 2012-09-28 15:51 ` htl10 at users dot sourceforge.net 2014-01-01 23:36 ` htl10 at users dot sourceforge.net 2014-06-13 11:50 ` 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-54448-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).