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 bootstrap/52840] bootstrap fails in libstdc++, missing compatibility.lo
Date: Tue, 17 Apr 2012 00:21:00 -0000 [thread overview]
Message-ID: <bug-52840-4-ILMN4tx0tO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52840-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52840
--- Comment #6 from Benjamin Kosnik <bkoz at gcc dot gnu.org> 2012-04-17 00:19:16 UTC ---
Author: bkoz
Date: Tue Apr 17 00:19:12 2012
New Revision: 186517
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=186517
Log:
2012-04-16 Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
PR bootstrap/52840
* src/Makefile.am (build-debug): Do not adjust vpath dir, remove
Makefile.tmp
* src/Makefile.in: Adjust as per above.
2012-04-16 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-list-2.cc: Guard with PIC.
* src/c++98/compatibility.cc: Tweak comments.
Added:
branches/gcc-4_7-branch/libstdc++-v3/src/c++11/compatibility-thread-c++0x.cc
Modified:
branches/gcc-4_7-branch/libstdc++-v3/ChangeLog
branches/gcc-4_7-branch/libstdc++-v3/libsupc++/Makefile.am
branches/gcc-4_7-branch/libstdc++-v3/libsupc++/Makefile.in
branches/gcc-4_7-branch/libstdc++-v3/src/Makefile.am
branches/gcc-4_7-branch/libstdc++-v3/src/Makefile.in
branches/gcc-4_7-branch/libstdc++-v3/src/c++11/Makefile.am
branches/gcc-4_7-branch/libstdc++-v3/src/c++11/Makefile.in
branches/gcc-4_7-branch/libstdc++-v3/src/c++11/compatibility-atomic-c++0x.cc
branches/gcc-4_7-branch/libstdc++-v3/src/c++11/compatibility-c++0x.cc
branches/gcc-4_7-branch/libstdc++-v3/src/c++11/future.cc
branches/gcc-4_7-branch/libstdc++-v3/src/c++11/mutex.cc
branches/gcc-4_7-branch/libstdc++-v3/src/c++98/Makefile.am
branches/gcc-4_7-branch/libstdc++-v3/src/c++98/Makefile.in
branches/gcc-4_7-branch/libstdc++-v3/src/c++98/compatibility-ldbl.cc
branches/gcc-4_7-branch/libstdc++-v3/src/c++98/compatibility-list-2.cc
branches/gcc-4_7-branch/libstdc++-v3/src/c++98/compatibility-list.cc
branches/gcc-4_7-branch/libstdc++-v3/src/c++98/compatibility.cc
prev parent reply other threads:[~2012-04-17 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 7:09 [Bug bootstrap/52840] New: " aldot at gcc dot gnu.org
2012-04-03 8:02 ` [Bug bootstrap/52840] " aldot at gcc dot gnu.org
2012-04-03 10:20 ` aldot at gcc dot gnu.org
2012-04-05 0:43 ` bkoz at gcc dot gnu.org
2012-04-05 7:01 ` aldot at gcc dot gnu.org
2012-04-05 7:03 ` aldot at gcc dot gnu.org
2012-04-17 0:21 ` bkoz at gcc dot gnu.org [this message]
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-52840-4-ILMN4tx0tO@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).