All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jordan Yelloz <jordan@yelloz.me>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] fwup: blanked out MANS to avoid running help2man
Date: Sun, 12 Jun 2016 22:26:40 -0700	[thread overview]
Message-ID: <20160613052640.6977-1-jordan@yelloz.me> (raw)
In-Reply-To: <20160613031101.27646-1-jordan@yelloz.me>

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.

Also, prevented anything but the fwup binary from being installed.

Signed-off-by: Jordan Yelloz <jordan@yelloz.me>
---
 package/fwup/fwup.mk | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/package/fwup/fwup.mk b/package/fwup/fwup.mk
index 0f857fc..26463e2 100644
--- a/package/fwup/fwup.mk
+++ b/package/fwup/fwup.mk
@@ -10,6 +10,8 @@ FWUP_LICENSE = Apache-2.0
 FWUP_LICENSE_FILES = LICENSE
 FWUP_DEPENDENCIES = libconfuse libarchive libsodium
 FWUP_AUTORECONF = YES
+FWUP_MAKE_OPTS = MANS=
+FWUP_INSTALL_TARGET_OPTS = install-exec DESTDIR=$(TARGET_DIR)
 
 define FWUP_ADD_M4_DIR
 	mkdir -p $(@D)/m4
-- 
2.8.4

  reply	other threads:[~2016-06-13  5:26 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   ` Jordan Yelloz [this message]
2016-06-13 21:51     ` [Buildroot] [PATCH v3 " 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
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=20160613052640.6977-1-jordan@yelloz.me \
    --to=jordan@yelloz.me \
    --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.