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: Sun, 15 Jun 2008 12:17:26 -0700 (PDT)	[thread overview]
Message-ID: <20080615191726.869EE3C920@busybox.net> (raw)

Author: jacmet
Date: 2008-06-15 12:17:23 -0700 (Sun, 15 Jun 2008)
New Revision: 22355

Log:
valgrind: needs kernel headers (and doesn't respect CFLAGS)


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


Changeset:
Modified: trunk/buildroot/package/valgrind/valgrind.mk
===================================================================
--- trunk/buildroot/package/valgrind/valgrind.mk	2008-06-15 19:17:14 UTC (rev 22354)
+++ trunk/buildroot/package/valgrind/valgrind.mk	2008-06-15 19:17:23 UTC (rev 22355)
@@ -25,6 +25,7 @@
 	(cd $(VALGRIND_DIR); rm -rf config.cache; \
 		$(TARGET_CONFIGURE_OPTS) \
 		$(TARGET_CONFIGURE_ARGS) \
+		CC="$(TARGET_CC) $(TARGET_CFLAGS) -I$(LINUX_HEADERS_DIR)/include" \
 		./configure \
 		--target=$(GNU_TARGET_NAME) \
 		--host=$(GNU_TARGET_NAME) \

             reply	other threads:[~2008-06-15 19:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-15 19:17 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
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=20080615191726.869EE3C920@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