public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David.Billinghurst@riotinto.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/3098: cygwin:  undefined reference to `___deregister_frame_info_bases
Date: Sat, 09 Jun 2001 12:16:00 -0000	[thread overview]
Message-ID: <20010609191050.30209.qmail@sourceware.cygnus.com> (raw)

>Number:         3098
>Category:       c++
>Synopsis:       cygwin:  undefined reference to `___deregister_frame_info_bases
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 09 12:16:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     David Billinghurst
>Release:        gcc 3.0 (pre-release)
>Organization:
>Environment:
i686-pc-cygwin
>Description:
This should be fixed before the 3.0 release.

On cygwin, many g++ (~600) and libstdc++-v3 (~40) tests fail with error:

/usr/local/obj/gcc/gcc/libgcc.a(unwind-dw2-fde.o): In function
`_deregister_frame': 
/usr/local/src/gcc/gcc/unwind-pe.h(.text+0x49b): undefined reference to
`___deregister_frame_info_bases'

This happens on both trunk and branch.

The problem is an additional leading underscore.

See:
  http://gcc.gnu.org/ml/gcc-bugs/2001-05/msg00842.html .
  http://gcc.gnu.org/ml/gcc-bugs/2001-05/msg00854.html 
>How-To-Repeat:
configure --enable-threads=posix
make check
>Fix:
Remove leading underscore.  Something like:

http://gcc.gnu.org/ml/gcc-bugs/2001-05/msg00854.html 
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-06-09 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-09 12:16 David.Billinghurst [this message]
2001-06-09 16:36 mmitchel
2001-06-11 13:19 rth

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=20010609191050.30209.qmail@sourceware.cygnus.com \
    --to=david.billinghurst@riotinto.com \
    --cc=gcc-gnats@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).