Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/valgrind
Date: Mon, 25 Sep 2006 01:48:47 -0700 (PDT)	[thread overview]
Message-ID: <20060925084847.87853486B2@busybox.net> (raw)

Author: jacmet
Date: 2006-09-25 01:48:47 -0700 (Mon, 25 Sep 2006)
New Revision: 16216

Log:
Valgrind works on PPC and AMD64 as well nowadays.
Use Kconfig to ensure valgrind can only be enabled on supported archs.


Modified:
   trunk/buildroot/package/valgrind/Config.in
   trunk/buildroot/package/valgrind/valgrind.mk


Changeset:
Modified: trunk/buildroot/package/valgrind/Config.in
===================================================================
--- trunk/buildroot/package/valgrind/Config.in	2006-09-25 07:38:13 UTC (rev 16215)
+++ trunk/buildroot/package/valgrind/Config.in	2006-09-25 08:48:47 UTC (rev 16216)
@@ -1,6 +1,7 @@
 config BR2_PACKAGE_VALGRIND
 	bool "valgrind"
 	default n
+	depends BR2_i386 || BR2_powerpc || BR2_x86_64
 	help
 	  Tool for debugging and profiling Linux programs.
 

Modified: trunk/buildroot/package/valgrind/valgrind.mk
===================================================================
--- trunk/buildroot/package/valgrind/valgrind.mk	2006-09-25 07:38:13 UTC (rev 16215)
+++ trunk/buildroot/package/valgrind/valgrind.mk	2006-09-25 08:48:47 UTC (rev 16216)
@@ -77,11 +77,7 @@
 	#cp $(VALGRIND_DIR)/woody.supp $(TARGET_DIR)/usr/lib/valgrind/
 	touch -c $(TARGET_DIR)/usr/bin/valgrind
 
-ifeq ($(BR2_i386),y)
 valgrind: $(TARGET_DIR)/usr/bin/valgrind
-else
-valgrind:
-endif
 
 valgrind-source: $(DL_DIR)/$(VALGRIND_SOURCE)
 

             reply	other threads:[~2006-09-25  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25  8:48 jacmet at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-01 19:09 [Buildroot] svn commit: trunk/buildroot/package/valgrind jacmet at uclibc.org
2008-06-15 20:44 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  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=20060925084847.87853486B2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox