From: Romain Izard <romain.izard.pro@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] core/pkg-kconfig: fix .config rule for silent mode
Date: Tue, 29 Mar 2016 12:11:41 +0200 [thread overview]
Message-ID: <1459246302-21837-2-git-send-email-romain.izard.pro@gmail.com> (raw)
In-Reply-To: <1459246302-21837-1-git-send-email-romain.izard.pro@gmail.com>
Ensure that each command line in the .config rule is prefixed by $$(Q)
Signed-off-by: Romain Izard <romain.izard.pro@gmail.com>
---
Changelog:
v2: New patch
package/pkg-kconfig.mk | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/pkg-kconfig.mk b/package/pkg-kconfig.mk
index 90f3f9f..94ec3cc 100644
--- a/package/pkg-kconfig.mk
+++ b/package/pkg-kconfig.mk
@@ -63,11 +63,11 @@ $$($(2)_KCONFIG_FILE) $$($(2)_KCONFIG_FRAGMENT_FILES): | $(1)-patch
# full .config first. We use 'make oldconfig' because this can be safely
# done even when the package does not support defconfigs.
$$($(2)_DIR)/.config: $$($(2)_KCONFIG_FILE) $$($(2)_KCONFIG_FRAGMENT_FILES)
- $$(if $$($(2)_KCONFIG_DEFCONFIG), \
+ $$(Q)$$(if $$($(2)_KCONFIG_DEFCONFIG), \
$$($(2)_MAKE_ENV) $$(MAKE) -C $$($(2)_DIR) \
$$($(2)_KCONFIG_OPTS) $$($(2)_KCONFIG_DEFCONFIG), \
cp $$($(2)_KCONFIG_FILE) $$(@))
- support/kconfig/merge_config.sh -m -O $$(@D) \
+ $$(Q)support/kconfig/merge_config.sh -m -O $$(@D) \
$$(@) $$($(2)_KCONFIG_FRAGMENT_FILES)
$$(Q)yes "" | $$($(2)_MAKE_ENV) $$(MAKE) -C $$($(2)_DIR) \
$$($(2)_KCONFIG_OPTS) oldconfig
--
2.5.0
next prev parent reply other threads:[~2016-03-29 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 10:11 [Buildroot] [PATCH v2 0/2] core/pkg-kconfig: Fix .config generation Romain Izard
2016-03-29 10:11 ` Romain Izard [this message]
2016-03-29 14:55 ` [Buildroot] [PATCH v2 1/2] core/pkg-kconfig: fix .config rule for silent mode Thomas Petazzoni
2016-03-29 10:11 ` [Buildroot] [PATCH v2 2/2] core/pkg-kconfig: Use oldnoconfig when possible Romain Izard
2016-03-30 20:30 ` Arnout Vandecappelle
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=1459246302-21837-2-git-send-email-romain.izard.pro@gmail.com \
--to=romain.izard.pro@gmail.com \
--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.