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 target/55061] libbacktrace build fails during bootstrap on powerpc-apple-darwin9 Date: Thu, 25 Oct 2012 13:47:00 -0000 [thread overview] Message-ID: <bug-55061-4-S9zbrDvbu2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55061-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55061 --- Comment #13 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-25 13:47:21 UTC --- % grep Unwind_GetIPInfo /usr/lib/gcc/powerpc-apple-darwin9/4.2.1/include/unwind.h % extern _Unwind_Ptr _Unwind_GetIPInfo (struct _Unwind_Context *, int *); % grep Unwind_GetIPInfo /usr/lib/gcc/powerpc-apple-darwin9/4.0.1/include/unwind.h % FYI, the original configure test for _Unwind_GetIPInfo was added in this PR26792... http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26792#c11 I think this is a latent issue created by this commit... r141804 | sje | 2008-11-12 16:35:46 -0500 (Wed, 12 Nov 2008) | 9 lines PR target/27880 * config/unwind_ipinfo.m4 (GCC_CHECK_UNWIND_GETIPINFO): Change from link test to target based test. * libstdc++/v3/configure.ac: Move call to GCC_CHECK_UNWIND_GETIPINFO. * libstdc++/v3/configure: Regenerate. * libjava/configure: Regenerate. which doesn't take in account that on darwin9 only the gcc-4.2.1 compiler provides _Unwind_GetIPInfo through /usr/lib/gcc/powerpc-apple-darwin9/4.2.1/include/unwind.h. This is a broken test since gcc-4.2.1 isn't the default system compiler on powerpc-apple-darwin9.
next prev parent reply other threads:[~2012-10-25 13:47 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-24 17:51 [Bug target/55061] New: " howarth at nitro dot med.uc.edu 2012-10-24 17:52 ` [Bug target/55061] " howarth at nitro dot med.uc.edu 2012-10-24 17:55 ` howarth at nitro dot med.uc.edu 2012-10-24 17:55 ` howarth at nitro dot med.uc.edu 2012-10-24 18:12 ` ian at airs dot com 2012-10-24 18:30 ` howarth at nitro dot med.uc.edu 2012-10-24 21:10 ` ian at gcc dot gnu.org 2012-10-24 21:12 ` ian at airs dot com 2012-10-25 1:13 ` howarth at nitro dot med.uc.edu 2012-10-25 3:34 ` ian at airs dot com 2012-10-25 13:14 ` howarth at nitro dot med.uc.edu 2012-10-25 13:16 ` howarth at nitro dot med.uc.edu 2012-10-25 13:33 ` howarth at nitro dot med.uc.edu 2012-10-25 13:47 ` howarth at nitro dot med.uc.edu [this message] 2012-10-25 14:12 ` howarth at nitro dot med.uc.edu 2012-10-25 15:05 ` howarth at nitro dot med.uc.edu 2012-10-25 17:37 ` ian at airs dot com 2012-10-25 17:41 ` ian at airs dot com 2012-10-25 17:57 ` howarth at nitro dot med.uc.edu 2012-10-25 18:55 ` ian at airs dot com 2012-10-25 19:38 ` howarth at nitro dot med.uc.edu 2012-10-25 19:57 ` howarth at nitro dot med.uc.edu 2012-10-25 22:35 ` howarth at nitro dot med.uc.edu 2012-10-25 23:09 ` howarth at nitro dot med.uc.edu 2012-10-25 23:51 ` ian at airs dot com 2012-10-26 3:31 ` howarth at nitro dot med.uc.edu 2012-10-26 17:35 ` ian at gcc dot gnu.org 2012-10-26 17:52 ` ian at airs dot com
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-55061-4-S9zbrDvbu2@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).