public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/27880] [4.2 regression] undefined reference to `_Unwind_GetIPInfo'
Date: Thu, 08 Jun 2006 22:26:00 -0000 [thread overview]
Message-ID: <20060608222517.31924.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27880-50@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from sje at cup dot hp dot com 2006-06-08 22:25 -------
I think using configure to detect whether or not _Unwind_GetIPInfo exists may
be difficult. The libstdc++ configure script seems to go out of its way to not
link programs or to use and/or look at libgcc in anyway.
Anyone have an idea on how to implement this? I am thinking the checking/flag
setting on whether or not _Unwind_GetIPInfo exists might have to be done in the
gcc directory.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27880
next prev parent reply other threads:[~2006-06-08 22:25 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 20:31 [Bug c/27880] New: " schwab at suse dot de
2006-06-02 20:33 ` [Bug c/27880] " schwab at suse dot de
2006-06-02 22:41 ` sje at cup dot hp dot com
2006-06-02 22:49 ` [Bug target/27880] " pinskia at gcc dot gnu dot org
2006-06-02 23:11 ` sje at cup dot hp dot com
2006-06-04 19:45 ` mmitchel at gcc dot gnu dot org
2006-06-06 4:00 ` geoffk at gcc dot gnu dot org
2006-06-08 22:26 ` sje at cup dot hp dot com [this message]
2006-06-21 10:09 ` schwab at suse dot de
2006-06-29 19:47 ` patchapp at dberlin dot org
2006-07-22 21:06 ` echristo at apple dot com
2006-07-22 21:41 ` schwab at suse dot de
2006-07-22 22:08 ` pinskia at gcc dot gnu dot org
2006-08-18 2:33 ` pinskia at gcc dot gnu dot org
2006-08-18 2:34 ` pinskia at gcc dot gnu dot org
2006-10-04 16:57 ` pinskia at gcc dot gnu dot org
2006-10-04 21:08 ` sje at cup dot hp dot com
2006-10-09 15:56 ` sje at gcc dot gnu dot org
2006-10-09 18:33 ` sje at cup dot hp dot com
2007-03-31 9:18 ` schwab at suse dot de
2007-03-31 9:29 ` schwab at suse dot de
2007-05-14 21:37 ` [Bug target/27880] [4.2/4.3 " mmitchel at gcc dot gnu dot org
2007-07-06 15:49 ` schwab at suse dot de
2007-07-20 3:50 ` mmitchel at gcc dot gnu dot org
2007-10-09 19:30 ` mmitchel at gcc dot gnu dot org
2007-10-16 16:19 ` patchapp at dberlin dot org
2008-01-18 9:22 ` bkoz at gcc dot gnu dot org
2008-02-01 16:54 ` jsm28 at gcc dot gnu dot org
2008-02-20 18:40 ` [Bug target/27880] [4.2/4.3/4.4 " ubizjak at gmail dot com
2008-03-04 17:56 ` wilson at tuliptree dot org
2008-04-22 7:51 ` vapier at gentoo dot org
2008-05-19 20:25 ` jsm28 at gcc dot gnu dot org
2008-06-23 4:34 ` russiane39 at gmail dot com
2008-09-06 22:51 ` pinskia at gcc dot gnu dot org
2008-09-06 22:55 ` doko at ubuntu dot com
2008-10-15 17:07 ` sje at cup dot hp dot com
2008-11-12 21:38 ` sje at gcc dot gnu dot org
2008-11-12 21:40 ` sje at gcc dot gnu dot org
2008-11-22 6:05 ` [Bug target/27880] [4.2/4.3 " cnstar9988 at gmail dot com
2009-01-03 19:55 ` rob1weld at aol dot com
2009-01-03 19:56 ` pinskia at gcc dot gnu dot org
2009-01-06 7:32 ` rob1weld at aol dot com
2009-03-31 19:37 ` [Bug target/27880] [4.3 " jsm28 at gcc dot gnu dot org
2009-08-04 12:34 ` rguenth at gcc dot gnu dot org
2010-05-22 18:35 ` rguenth at gcc dot gnu dot 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=20060608222517.31924.qmail@sourceware.org \
--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: link
Be 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).