From: Markus Mayer <code@mmayer.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/linux-tools: set PKG_CONFIG for tmon builds
Date: Tue, 26 Sep 2017 12:08:59 -0700 [thread overview]
Message-ID: <20170926190859.4015-1-code@mmayer.net> (raw)
From: Markus Mayer <mmayer@broadcom.com>
We ensure that PKG_CONFIG is set to buildroot's host version of
pkg-config. This is done by passing TARGET_CONFIGURE_OPTS instead of
TARGET_MAKE_ENV to make. The former includes
PKG_CONFIG="$(PKG_CONFIG_HOST_BINARY)"
while the latter doesn't.
Signed-off-by: Markus Mayer <mmayer@broadcom.com>
---
package/linux-tools/linux-tool-tmon.mk.in | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/package/linux-tools/linux-tool-tmon.mk.in b/package/linux-tools/linux-tool-tmon.mk.in
index 15931c3..b62f547 100644
--- a/package/linux-tools/linux-tool-tmon.mk.in
+++ b/package/linux-tools/linux-tool-tmon.mk.in
@@ -8,8 +8,7 @@ LINUX_TOOLS += tmon
TMON_DEPENDENCIES = host-pkgconf ncurses
TMON_MAKE_OPTS = $(LINUX_MAKE_FLAGS) \
- CC=$(TARGET_CC) \
- PKG_CONFIG_PATH=$(STAGING_DIR)/usr/lib/pkgconfig
+ CC=$(TARGET_CC)
ifeq ($(BR2_TOOLCHAIN_HAS_SSP),)
define TMON_DISABLE_STACK_PROTECTOR
@@ -24,13 +23,13 @@ define TMON_BUILD_CMDS
exit 1 ; \
fi
$(TMON_DISABLE_STACK_PROTECTOR)
- $(TARGET_MAKE_ENV) $(MAKE) -C $(LINUX_DIR)/tools \
+ $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(LINUX_DIR)/tools \
$(TMON_MAKE_OPTS) \
tmon
endef
define TMON_INSTALL_TARGET_CMDS
- $(TARGET_MAKE_ENV) $(MAKE) -C $(LINUX_DIR)/tools \
+ $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(LINUX_DIR)/tools \
$(TMON_MAKE_OPTS) \
INSTALL_ROOT=$(TARGET_DIR) \
tmon_install
--
2.7.4
next reply other threads:[~2017-09-26 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 19:08 Markus Mayer [this message]
2017-09-26 19:53 ` [Buildroot] [PATCH] package/linux-tools: set PKG_CONFIG for tmon builds Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2017-09-26 18:03 Markus Mayer
2017-09-26 19:23 ` Markus Mayer
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=20170926190859.4015-1-code@mmayer.net \
--to=code@mmayer.net \
--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