public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/54806] [4.7 Regression] Undefined symbols: "___emutls_v.*", ... on x86_64-apple-darwin12 Date: Sat, 06 Oct 2012 17:00:00 -0000 [thread overview] Message-ID: <bug-54806-4-tp5GeBgjKc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54806-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54806 --- Comment #14 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-06 17:00:17 UTC --- Interestingly Macports' libgomp shows the same expected emutls related symbols as fink... % nm libgomp.1.dylib | grep emutls U ___emutls_get_address 000000000000b1e0 d ___emutls_v.gomp_tls_data I suspect the absence of ___emutls_v.* symbols in the MacPorts gcc47's libstdc++.6.dylib could be due to the fact that clang is used to build it rather than a proper full bootstrap. Please try restoring the bootstrap and see if the symbols are restored to libstdc++.6.dylib.
next prev parent reply other threads:[~2012-10-06 17:00 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-04 1:10 [Bug middle-end/54806] New: [4.7.2 Regression] Undefined symbols: "___emutls_v.*", ... on *-apple-darwin* whatmannerofburgeristhis at gmail dot com 2012-10-04 1:10 ` [Bug middle-end/54806] " whatmannerofburgeristhis at gmail dot com 2012-10-04 12:10 ` [Bug middle-end/54806] [4.7 " rguenth at gcc dot gnu.org 2012-10-04 13:44 ` dominiq at lps dot ens.fr 2012-10-04 17:35 ` whatmannerofburgeristhis at gmail dot com 2012-10-04 20:37 ` [Bug middle-end/54806] [4.7 Regression] Undefined symbols: "___emutls_v.*", ... on x86_64-apple-darwin12 dominiq at lps dot ens.fr 2012-10-05 5:41 ` whatmannerofburgeristhis at gmail dot com 2012-10-05 14:33 ` howarth at nitro dot med.uc.edu 2012-10-05 14:58 ` howarth at nitro dot med.uc.edu 2012-10-05 17:41 ` jeremyhu at macports dot org 2012-10-05 17:47 ` jeremyhu at macports dot org 2012-10-06 0:47 ` howarth at nitro dot med.uc.edu 2012-10-06 0:56 ` howarth at nitro dot med.uc.edu 2012-10-06 1:46 ` howarth at nitro dot med.uc.edu 2012-10-06 6:39 ` jeremyhu at macports dot org 2012-10-06 17:00 ` howarth at nitro dot med.uc.edu [this message] 2012-10-06 17:27 ` howarth at nitro dot med.uc.edu 2012-10-06 17:48 ` jeremyhu at macports dot org 2012-10-06 19:27 ` howarth at nitro dot med.uc.edu 2012-10-06 19:53 ` jeremyhu at macports dot org 2012-10-06 20:57 ` howarth at nitro dot med.uc.edu 2012-10-06 21:06 ` howarth at nitro dot med.uc.edu 2012-10-06 21:14 ` jeremyhu at macports dot org 2012-10-06 21:15 ` jeremyhu at macports dot org 2012-10-07 10:51 ` dominiq at lps dot ens.fr
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-54806-4-tp5GeBgjKc@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).