public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: dnovillo@google.com (Diego Novillo)
To: reply@codereview.appspotmail.com, xur@google.com,
	gcc-patches@gcc.gnu.org
Subject: [google] Install additional gcov files (issue4442052)
Date: Sat, 16 Apr 2011 20:25:00 -0000	[thread overview]
Message-ID: <20110416201432.2E99DAE18B@tobiano.tor.corp.google.com> (raw)

I'm committing this patch from Rong Xu.  These added files are used
for FDO kernel builds.

Rong, could you please provide more details?  Will you be submitting
this patch to trunk?

Tested on x86_64.  Committed to google/main branch.

Thanks.  Diego.

2011-04-15  Rong Xu  <xur@google.com>
    
    	* Makefile.in (install-leaf): Install gcov-io.h, gcov-iov.h
    	gcov-io.c and libgcov.c to $DESTDIR/$inst_libdir/gcov-src.

diff --git a/libgcc/Makefile.in b/libgcc/Makefile.in
index 7e2ab93..3a3c936 100644
--- a/libgcc/Makefile.in
+++ b/libgcc/Makefile.in
@@ -978,6 +978,18 @@ install-leaf: $(install-shared) $(install-libunwind)
 	  esac;							\
 	done
 
+	if [ "$(MULTIDIR)" == "." ]; then                       \
+	  gcov_src_dest="$(DESTDIR)$(inst_libdir)/gcov-src";    \
+	  $(mkinstalldirs) $$gcov_src_dest;                     \
+	  cp ../../gcc/gcov-iov.h $$gcov_src_dest;              \
+	  cp $(srcdir)/../gcc/gcov-io.h $$gcov_src_dest;        \
+	  cp $(srcdir)/../gcc/gcov-io.c $$gcov_src_dest;        \
+	  cp $(srcdir)/../gcc/libgcov.c $$gcov_src_dest;        \
+	  chmod 644 $$gcov_src_dest/gcov-iov.h                  \
+	    $$gcov_src_dest/gcov-io.h $$gcov_src_dest/gcov-io.c \
+	    $$gcov_src_dest/libgcov.c;                          \
+	fi
+
 install: install-leaf
 	@: $(MAKE) ; $(MULTIDO) $(FLAGS_TO_PASS) multi-do DO=install
 


--
This patch is available for review at http://codereview.appspot.com/4442052

             reply	other threads:[~2011-04-16 20:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-16 20:25 Diego Novillo [this message]
2011-04-17  7:32 ` Ralf Wildenhues

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=20110416201432.2E99DAE18B@tobiano.tor.corp.google.com \
    --to=dnovillo@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=reply@codereview.appspotmail.com \
    --cc=xur@google.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).