From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] binutils: disable makeinfo
Date: Tue, 1 Jul 2014 15:16:31 +0200 [thread overview]
Message-ID: <20140701141340.0C16D9D090@busybox.osuosl.org> (raw)
commit: http://git.buildroot.net/buildroot/commit/?id=0c7db694ac1292167ffc23f372dd1af1918e312b
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
makeinfo is known to cause problems when building old texi files with more
recent host makeinfo.
In particular binutils-2.18 won't build on Fedora 20 without this change.
Even though more up to date binutils does build without this change there's
no guaranty it will with bump of host makeinfo in the future.
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Cc: Anton Kolesov <akolesov@synopsys.com>
Cc: Peter Korsgaard <peter@korsgaard.com>
Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
package/binutils/binutils.mk | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/package/binutils/binutils.mk b/package/binutils/binutils.mk
index 9cc4d28..77d0751 100644
--- a/package/binutils/binutils.mk
+++ b/package/binutils/binutils.mk
@@ -49,6 +49,11 @@ BINUTILS_CONF_OPT = --disable-multilib --disable-werror \
--enable-install-libiberty \
$(BINUTILS_EXTRA_CONFIG_OPTIONS)
+# Don't build documentation. It takes up extra space / build time,
+# and sometimes needs specific makeinfo versions to work
+BINUTILS_CONF_ENV += ac_cv_prog_MAKEINFO=missing
+HOST_BINUTILS_CONF_ENV += ac_cv_prog_MAKEINFO=missing
+
# Install binutils after busybox to prefer full-blown utilities
ifeq ($(BR2_PACKAGE_BUSYBOX),y)
BINUTILS_DEPENDENCIES += busybox
reply other threads:[~2014-07-01 13:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140701141340.0C16D9D090@busybox.osuosl.org \
--to=peter@korsgaard.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.