From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libtool: disable makeinfo
Date: Fri, 3 Jul 2015 18:07:54 +0200 [thread overview]
Message-ID: <5596B35A.2020804@mind.be> (raw)
In-Reply-To: <e64f1903478b53f185f3bf114f86c46948a31311.1435886073.git.sam.bobroff@au1.ibm.com>
On 07/03/15 03:14, Sam Bobroff wrote:
> host-libtool can fail to build if the host is missing makeinfo, so
> disable it.
>
> Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
> ---
> Without this patch, buildroot fails to build host-libtool on my Debian
> 8 system, as it doesn't have the texinfo package installed.
>
> package/libtool/libtool.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/libtool/libtool.mk b/package/libtool/libtool.mk
> index 28786d2..8688f8b 100644
> --- a/package/libtool/libtool.mk
> +++ b/package/libtool/libtool.mk
> @@ -13,6 +13,7 @@ LIBTOOL_DEPENDENCIES = host-m4
> LIBTOOL_LICENSE = GPLv2+
> LIBTOOL_LICENSE_FILES = COPYING
>
> +HOST_LIBTOOL_CONF_ENV = MAKEINFO=true
> HOST_LIBTOOL_LIBTOOL_PATCH = NO
>
> # We have a patch that affects libtool.m4, which triggers an autoreconf
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-07-03 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 1:14 [Buildroot] [PATCH 1/1] package/libtool: disable makeinfo Sam Bobroff
2015-07-03 16:07 ` Arnout Vandecappelle [this message]
2015-07-03 17:56 ` Yann E. MORIN
2015-07-04 10:45 ` Thomas Petazzoni
2015-07-06 21:37 ` Arnout Vandecappelle
2015-07-07 6:20 ` Peter Korsgaard
2015-07-07 7:22 ` Thomas Petazzoni
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=5596B35A.2020804@mind.be \
--to=arnout@mind.be \
--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