From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libcec: disable build infos
Date: Wed, 18 Apr 2018 23:13:30 +0200 [thread overview]
Message-ID: <20180418211330.13594-1-romain.naour@gmail.com> (raw)
Build infos can break the build due to missing terminating " character.
Fixes:
http://autobuild.buildroot.net/results/3b1/3b1182783fc958dfed96c6b1c097993662fc7308
Signed-off-by: Romain Naour <romain.naour@gmail.com>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>
---
package/libcec/libcec.mk | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/package/libcec/libcec.mk b/package/libcec/libcec.mk
index 6d14447958..99d1c8b2ba 100644
--- a/package/libcec/libcec.mk
+++ b/package/libcec/libcec.mk
@@ -37,4 +37,11 @@ ifeq ($(BR2_PACKAGE_XLIB_LIBXRANDR),y)
LIBCEC_DEPENDENCIES += xlib_libXrandr
endif
+# Disable information about how libCEC is compiled.
+LIBCEC_CONF_OPTS += -DHAVE_GIT_BIN="" \
+ -DHAVE_DATE_BIN="" \
+ -DHAVE_WHOAMI_BIN="" \
+ -DHAVE_HOSTNAME_BIN="" \
+ -DHAVE_UNAME_BIN=""
+
$(eval $(cmake-package))
--
2.14.3
next reply other threads:[~2018-04-18 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 21:13 Romain Naour [this message]
2018-04-19 21:35 ` [Buildroot] [PATCH] package/libcec: disable build infos Thomas Petazzoni
2018-05-01 6:54 ` Peter Korsgaard
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=20180418211330.13594-1-romain.naour@gmail.com \
--to=romain.naour@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox