public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/52689] static linking with libstdc++ fails Date: Thu, 29 Mar 2012 06:36:00 -0000 [thread overview] Message-ID: <bug-52689-4-3WM6pTgWfY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52689-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52689 --- Comment #9 from Benjamin Kosnik <bkoz at gcc dot gnu.org> 2012-03-29 06:14:41 UTC --- Author: bkoz Date: Thu Mar 29 06:14:32 2012 New Revision: 185950 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=185950 Log: 2012-03-28 Benjamin Kosnik <bkoz@redhat.com> PR libstdc++/52689 * libsupc++/Makefile.am (LTCXXCOMPILE, CXXLINK): Tweak. * libsupc++/Makefile.in: Regenerated. * src/Makefile.am (LTCXXCOMPILE, CXXLINK): Tweak. (libstdc___la_SOURCES): Add in compatiblity files, with content that varies with -DPIC. * src/Makefile.in: Regenerated. * src/c++11/Makefile.am (LTCXXCOMPILE, CXXLINK): Tweak. * src/c++11/Makefile.in: Regenerated. * src/c++11/compatibility-atomic-c++0x.cc: Guard with PIC. * src/c++11/compatibility-c++0x.cc: Same. * src/c++11/future.cc: Consolidate compatibility bits into.. * src/c++11/mutex.cc: Consolidate compatibility bits into.. * src/c++11/compatibility-thread-cxx0x.cc: ...here. New. * src/c++98/Makefile.am (LTCXXCOMPILE, CXXLINK): Tweak. * src/c++98/Makefile.in: Regenerated. * src/c++98/compatibility-ldbl.cc: Guard with PIC * src/c++98/compatibility-list-2.cc: Same. * src/c++98/compatibility-list.cc: Same. * src/c++98/compatibility.cc: Tweak comments. Added: trunk/libstdc++-v3/src/c++11/compatibility-thread-c++0x.cc - copied, changed from r185946, trunk/libstdc++-v3/src/c++11/mutex.cc Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/libsupc++/Makefile.am trunk/libstdc++-v3/libsupc++/Makefile.in trunk/libstdc++-v3/src/Makefile.am trunk/libstdc++-v3/src/Makefile.in trunk/libstdc++-v3/src/c++11/Makefile.am trunk/libstdc++-v3/src/c++11/Makefile.in trunk/libstdc++-v3/src/c++11/compatibility-atomic-c++0x.cc trunk/libstdc++-v3/src/c++11/compatibility-c++0x.cc trunk/libstdc++-v3/src/c++11/future.cc trunk/libstdc++-v3/src/c++11/mutex.cc trunk/libstdc++-v3/src/c++98/Makefile.am trunk/libstdc++-v3/src/c++98/Makefile.in trunk/libstdc++-v3/src/c++98/compatibility-ldbl.cc trunk/libstdc++-v3/src/c++98/compatibility-list-2.cc trunk/libstdc++-v3/src/c++98/compatibility-list.cc trunk/libstdc++-v3/src/c++98/compatibility.cc
next prev parent reply other threads:[~2012-03-29 6:15 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-23 17:31 [Bug libstdc++/52689] New: " jens.maurer at gmx dot net 2012-03-23 17:32 ` [Bug libstdc++/52689] " markus at trippelsdorf dot de 2012-03-23 20:14 ` jens.maurer at gmx dot net 2012-03-23 20:21 ` jens.maurer at gmx dot net 2012-03-23 21:19 ` markus at trippelsdorf dot de 2012-03-24 20:21 ` markus at trippelsdorf dot de 2012-03-27 7:32 ` jens.maurer at gmx dot net 2012-03-27 7:35 ` markus at trippelsdorf dot de 2012-03-27 15:37 ` jakub at gcc dot gnu.org 2012-03-29 6:36 ` bkoz at gcc dot gnu.org [this message] 2012-03-30 17:24 ` ro at gcc dot gnu.org 2012-04-03 8:01 ` ubizjak at gmail dot com 2012-04-03 8:57 ` ubizjak at gmail dot com 2012-04-03 9:47 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-04-04 17:06 ` bkoz at gcc dot gnu.org 2012-04-04 17:24 ` bkoz at gcc dot gnu.org 2012-04-04 17:27 ` uros at gcc dot gnu.org 2012-04-17 0:20 ` bkoz at gcc dot gnu.org 2012-04-17 2:23 ` bkoz at gcc dot gnu.org 2012-04-25 1:18 ` bkoz at gcc dot gnu.org 2012-04-25 2:01 ` bkoz at gcc dot gnu.org 2012-04-25 22:48 ` bkoz at gcc dot gnu.org 2012-05-02 22:44 ` bkoz at gcc dot gnu.org 2012-06-15 10:39 ` redi 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-52689-4-3WM6pTgWfY@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).