public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gseanmcg at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/50715] bootstrap fails in libstdc++-v3 with error on symbol versioning linker script when using Sun ld
Date: Fri, 14 Oct 2011 15:04:00 -0000	[thread overview]
Message-ID: <bug-50715-4-6ox4aI1Xim@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50715-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50715

Sean McGovern <gseanmcg at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|bootstrap fails with error  |bootstrap fails in
                   |on symbol versioning linker |libstdc++-v3 with error on
                   |script when using Sun ld    |symbol versioning linker
                   |                            |script when using Sun ld

--- Comment #5 from Sean McGovern <gseanmcg at gmail dot com> 2011-10-14 15:04:04 UTC ---
Probably broken by 179769:

Author: bkoz
Date: Mon Oct 10 19:03:39 2011
New Revision: 179769

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=179769
Log:
2011-10-10  Benjamin Kosnik  <bkoz@redhat.com>

    PR libstdc++/49818
    * config/abi/pre/gnu.ver (CXXABI_1.3.6): Add symbols.
    * testsuite/util/testsuite_abi.cc: Same.
    * libsupc++/unwind-cxx.h: Move required eh API...
    * libsupc++/cxxabi.h: ... to here. Add required forward declarations.
    Use _GLIBCXX_NOTHROW.
    * libsupc++/pure.cc (__cxa_deleted_virtual): Add.
    * libsupc++/eh_alloc.cc: Use _GLIBCXX_NOTHROW.
    * libsupc++/eh_catch.cc: Same.
    * libsupc++/eh_globals.cc: Same.
    * libsupc++/eh_type.cc: Same.

Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/config/abi/pre/gnu.ver
    trunk/libstdc++-v3/libsupc++/cxxabi.h
    trunk/libstdc++-v3/libsupc++/eh_alloc.cc
    trunk/libstdc++-v3/libsupc++/eh_catch.cc
    trunk/libstdc++-v3/libsupc++/eh_globals.cc
    trunk/libstdc++-v3/libsupc++/eh_type.cc
    trunk/libstdc++-v3/libsupc++/pure.cc
    trunk/libstdc++-v3/libsupc++/unwind-cxx.h
    trunk/libstdc++-v3/testsuite/util/testsuite_abi.cc


  parent reply	other threads:[~2011-10-14 15:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 14:57 [Bug bootstrap/50715] New: build with --enable-checking=release fails with linker error gseanmcg at gmail dot com
2011-10-13 17:46 ` [Bug bootstrap/50715] " gseanmcg at gmail dot com
2011-10-13 17:52 ` gseanmcg at gmail dot com
2011-10-14 13:30 ` [Bug bootstrap/50715] bootstrap fails with error on symbol versioning linker script when using Sun ld gseanmcg at gmail dot com
2011-10-14 13:33 ` gseanmcg at gmail dot com
2011-10-14 15:04 ` gseanmcg at gmail dot com [this message]
2011-10-14 15:25 ` [Bug bootstrap/50715] [4.7 regression] bootstrap fails in libstdc++-v3 " ro at gcc dot gnu.org
2011-10-14 15:32 ` paolo.carlini at oracle dot com
2011-10-14 15:58 ` ro at gcc dot gnu.org
2011-10-14 16:02 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-10-17 13:19 ` gseanmcg at gmail dot com
2011-10-17 14:55 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-10-17 15:03 ` ro at gcc dot gnu.org
2011-10-17 15:16 ` ro at gcc dot gnu.org
2011-10-17 15:16 ` 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-50715-4-6ox4aI1Xim@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: 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).