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] many failures with /sbin/loader: Error: libstdc++.so.6: symbol "__pthread_mutex_init" unresolved Date: Wed, 01 Jan 2014 23:36:00 -0000 [thread overview] Message-ID: <bug-54448-4-IrEF8eM5VM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54448-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54448 --- Comment #6 from Hin-Tak Leung <htl10 at users dot sourceforge.net> --- The latest with 4.6.4 and 4.7.3 : http://gcc.gnu.org/ml/gcc-testresults/2014-01/msg00048.html http://gcc.gnu.org/ml/gcc-testresults/2014-01/msg00049.html seems to be a lot healthier. During the course of the latest round, I realised that it seems that GNU strip from GNU binutils seems to confuse the configure system (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44959 bootstrap failed at Comparing stages 2 and 3) on -gtoggle ; so I am putting /usr/local/bin *last*, instead of first as previously. gcc these days requires GNU tar to extract, and GNU make, GNU bash to configure and make, so it is almost a habit to put /usr/local/bin first, but GNU strip certainly seems to behave differently from DEC strip. Would any of GNU binutils causes "/sbin/loader: Error: libstdc++.so.6: symbol "__pthread_mutex_init" unresolved"? If there is a simple test, I can try.
next prev parent reply other threads:[~2014-01-01 23:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-01 8:58 [Bug libstdc++/54448] New: " htl10 at users dot sourceforge.net 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 [this message] 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-IrEF8eM5VM@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).