use pkg-config to add valgrind include path

makes knowledge of VALGRIND_VALGRIND_H vs. VALGRIND_H optional

boards/native/Makefile.include

@@ -22,7 +22,8 @@ export LINKFLAGS += -m32 -gc -ldl
 export ASFLAGS =
 export DEBUGGER_FLAGS = $(ELF)
 export VALGRIND_FLAGS ?= --track-origins=yes
-all-valgrind: export CFLAGS += -DHAVE_VALGRIND_VALGRIND_H -g
+all-valgrind: export CFLAGS += -DHAVE_VALGRIND_H -g
+all-valgrind: export INCLUDES += $(shell pkg-config valgrind --cflags)
 
 # backward compatability with glibc <= 2.17 for native
 ifeq ($(CPU),native)

cpu/native/README

@@ -32,14 +32,6 @@ As root call:
 
     echo 0 > /proc/sys/kernel/yama/ptrace_scope
 
-PS:
-If the all-valgrind make target fails you might have to adjust the
-headers path. Change the parameter in boards/native/Makefile.include
-from HAVE_VALGRIND_VALGRIND_H to HAVE_VALGRIND_H to resolve the
-situation locally and open an issue to get it resolved permanently. (I
-have not yet encountered a platform that actually uses the other
-header path.)
-
 
 NETWORK SUPPORT
 ===============

dist/Makefile

@@ -23,13 +23,9 @@ export RIOTBASE ?= $(CURDIR)/../../RIOT
 # Uncomment this to enable scheduler statistics for ps:
 #CFLAGS += -DSCHEDSTATISTICS
 
-# If you want to use valgrind, you should recompile native with either
-# HAVE_VALGRIND_H or HAVE_VALGRIND_VALGRIND_H depending on the location
-# of the valgrind header (i.e. <valgrind.h> or <valgrind/valgrind.h>)
-# For more information about the valgrind support of RIOT read:
-# RIOT/cpu/native/README
-#CFLAGS += -DHAVE_VALGRIND_VALGRIND_H
-#CFLAGS += -DHAVE_VALGRIND_H
+# If you want to use native with valgrind, you should recompile native
+# with the target all-valgrind instead of all:
+# make -B clean all-valgrind
 
 # Uncomment this to enable code in RIOT that does safety checking
 # which is not needed in a production environment but helps in the