From: Frank Hunleth <fhunleth@troodon-software.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] fwup: blanked out HELP2MAN_PATH autoconf value
Date: Tue, 14 Jun 2016 09:45:51 -0400 [thread overview]
Message-ID: <CA+-urNQZ-Z_UfCx9xXeT0MFApQWgce0owVKrPYEE_akrXVq7Ug@mail.gmail.com> (raw)
In-Reply-To: <20160613221507.29556-1-jordan@yelloz.me>
On Mon, Jun 13, 2016 at 6:15 PM, Jordan Yelloz <jordan@yelloz.me> wrote:
> If you have help2man installed, the build system will try to run
> help2man on the target fwup binary which should not be expected to work.
>
> Signed-off-by: Jordan Yelloz <jordan@yelloz.me>
> ---
> package/fwup/fwup.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/fwup/fwup.mk b/package/fwup/fwup.mk
> index 0f857fc..814ca00 100644
> --- a/package/fwup/fwup.mk
> +++ b/package/fwup/fwup.mk
> @@ -10,6 +10,7 @@ FWUP_LICENSE = Apache-2.0
> FWUP_LICENSE_FILES = LICENSE
> FWUP_DEPENDENCIES = libconfuse libarchive libsodium
> FWUP_AUTORECONF = YES
> +FWUP_CONF_ENV = ac_cv_path_HELP2MAN=
This change fixes the issue with help2man being installed on the host for me.
Tested-by: Frank Hunleth <fhunleth@troodon-software.com>
>
> define FWUP_ADD_M4_DIR
> mkdir -p $(@D)/m4
> --
> 2.8.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2016-06-14 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 2:38 [Buildroot] [PATCH 1/1] fwup: blanked out MANS to avoid running help2man Jordan Yelloz
2016-06-13 3:11 ` [Buildroot] [PATCH v2 " Jordan Yelloz
2016-06-13 5:26 ` [Buildroot] [PATCH v3 " Jordan Yelloz
2016-06-13 21:51 ` Frank Hunleth
2016-06-13 22:09 ` Jordan Yelloz
2016-06-13 22:15 ` [Buildroot] [PATCH v4 1/1] fwup: blanked out HELP2MAN_PATH autoconf value Jordan Yelloz
2016-06-14 13:45 ` Frank Hunleth [this message]
2016-06-13 3:13 ` [Buildroot] [PATCH v2 1/1] iptables: exported AR=$(TARGET_AR) to make Jordan Yelloz
2016-07-05 13:03 ` 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=CA+-urNQZ-Z_UfCx9xXeT0MFApQWgce0owVKrPYEE_akrXVq7Ug@mail.gmail.com \
--to=fhunleth@troodon-software.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.