From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/valgrind
Date: Tue, 1 Jul 2008 12:09:52 -0700 (PDT) [thread overview]
Message-ID: <20080701190953.0C51D3C678@busybox.net> (raw)
Author: jacmet
Date: 2008-07-01 12:09:50 -0700 (Tue, 01 Jul 2008)
New Revision: 22596
Log:
valgrind: don't remove TARGET_DIR/usr/lib/pkgconfig
There's no need for removing the pkgconfig files in valgrind.mk
as that is now handled by the generic BR2_HAVE_DEVFILES.
Modified:
trunk/buildroot/package/valgrind/valgrind.mk
Changeset:
Modified: trunk/buildroot/package/valgrind/valgrind.mk
===================================================================
--- trunk/buildroot/package/valgrind/valgrind.mk 2008-07-01 16:09:07 UTC (rev 22595)
+++ trunk/buildroot/package/valgrind/valgrind.mk 2008-07-01 19:09:50 UTC (rev 22596)
@@ -64,11 +64,6 @@
cp package/valgrind/valgrind.sh $(TARGET_DIR)/usr/bin/valgrind
chmod a+x $(TARGET_DIR)/usr/bin/valgrind
rm -rf $(TARGET_DIR)/usr/share/doc/valgrind
- rm -rf $(TARGET_DIR)/usr/lib/pkgconfig
- #mkdir -p $(TARGET_DIR)/etc/default
- #cp $(VALGRIND_DIR)/valgrind.default $(TARGET_DIR)/etc/default/valgrind
- #mkdir -p $(TARGET_DIR)/usr/lib/valgrind
- #cp $(VALGRIND_DIR)/woody.supp $(TARGET_DIR)/usr/lib/valgrind/
touch -c $@
valgrind: $(TARGET_DIR)/usr/bin/valgrind
next reply other threads:[~2008-07-01 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 19:09 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-15 20:44 [Buildroot] svn commit: trunk/buildroot/package/valgrind jacmet at uclibc.org
2008-06-16 7:54 ` Bernhard Fischer
2008-06-16 8:03 ` Peter Korsgaard
2008-06-15 20:44 jacmet at uclibc.org
2008-06-15 19:17 jacmet at uclibc.org
2007-07-05 15:55 jacmet at uclibc.org
2007-04-03 15:36 jacmet at uclibc.org
2006-09-25 8:48 jacmet at uclibc.org
2006-09-25 7:27 jacmet at uclibc.org
2006-08-10 20:21 andersen at uclibc.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=20080701190953.0C51D3C678@busybox.net \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.