From: dnovillo@google.com (Diego Novillo)
To: reply@codereview.appspotmail.com, dougkwan@google.com,
libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [google] Install cpu_defines.h (issue4440044)
Date: Sat, 16 Apr 2011 22:11:00 -0000 [thread overview]
Message-ID: <20110416202739.6D629AE18B@tobiano.tor.corp.google.com> (raw)
I am committing this patch from Doug Kwan on google/main.
This patch adds cpu_defines.h to the set of files to be installed.
Doug, could you describe why we need to do this? Will you be
submitting this patch for trunk?
Tested on x86_64. Committed on google/main.
Diego.
2011-03-15 Doug Kwan <dougkwan@google.com>
Google ref 50044.
PR libstdc++/48123
* include/Makefile.am (install-freestanding-headers): Install
cpu_defines.h
* include/Makefile.in: Regenerate.
diff --git a/libstdc++-v3/include/Makefile.am b/libstdc++-v3/include/Makefile.am
index e7f1543..d3b44bc 100644
--- a/libstdc++-v3/include/Makefile.am
+++ b/libstdc++-v3/include/Makefile.am
@@ -1201,7 +1201,8 @@ endif
install-freestanding-headers:
$(mkinstalldirs) $(DESTDIR)${gxx_include_dir}
$(mkinstalldirs) $(DESTDIR)${host_installdir}
- for file in ${host_srcdir}/os_defines.h ${host_builddir}/c++config.h; do \
+ for file in ${host_srcdir}/os_defines.h ${host_builddir}/c++config.h \
+ ${glibcxx_srcdir}/$(CPU_DEFINES_SRCDIR)/cpu_defines.h; do \
$(INSTALL_DATA) $${file} $(DESTDIR)${host_installdir}; done
$(mkinstalldirs) $(DESTDIR)${gxx_include_dir}/${std_builddir}
$(INSTALL_DATA) ${std_builddir}/limits $(DESTDIR)${gxx_include_dir}/${std_builddir}
diff --git a/libstdc++-v3/include/Makefile.in b/libstdc++-v3/include/Makefile.in
index a93b2ea..8a23c1b 100644
--- a/libstdc++-v3/include/Makefile.in
+++ b/libstdc++-v3/include/Makefile.in
@@ -1585,7 +1585,8 @@ ${pch3_output}: ${pch3_source} ${pch2_output}
install-freestanding-headers:
$(mkinstalldirs) $(DESTDIR)${gxx_include_dir}
$(mkinstalldirs) $(DESTDIR)${host_installdir}
- for file in ${host_srcdir}/os_defines.h ${host_builddir}/c++config.h; do \
+ for file in ${host_srcdir}/os_defines.h ${host_builddir}/c++config.h \
+ ${glibcxx_srcdir}/$(CPU_DEFINES_SRCDIR)/cpu_defines.h; do \
$(INSTALL_DATA) $${file} $(DESTDIR)${host_installdir}; done
$(mkinstalldirs) $(DESTDIR)${gxx_include_dir}/${std_builddir}
$(INSTALL_DATA) ${std_builddir}/limits $(DESTDIR)${gxx_include_dir}/${std_builddir}
--
This patch is available for review at http://codereview.appspot.com/4440044
next reply other threads:[~2011-04-16 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 22:11 Diego Novillo [this message]
2011-04-19 16:38 ` Benjamin Kosnik
2011-04-19 16:42 ` Diego Novillo
2011-04-19 17:38 ` Doug Kwan (關振德)
2011-04-19 17:49 ` Paolo Carlini
2011-04-19 18:20 ` Doug Kwan (關振德)
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=20110416202739.6D629AE18B@tobiano.tor.corp.google.com \
--to=dnovillo@google.com \
--cc=dougkwan@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=reply@codereview.appspotmail.com \
/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).