From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/luksmeta: do not build man pages
Date: Mon, 16 Sep 2019 15:50:48 +0200 [thread overview]
Message-ID: <20190916135048.5459-1-peter@korsgaard.com> (raw)
Fixes:
http://autobuild.buildroot.net/results/a6247b95f1578fe1daec485589582310c75b5d84/
luksmeta-v9 generates man pages at build if a2x is available since:
commit 3fa51bb22350fee101fc52044949f6eb394114ae
Author: Daniel Kope?ek <dkopecek@redhat.com>
Date: Fri Jul 13 01:52:45 2018 +0200
Generate manual page from source during build time
If a2x (asciidoc) is not available during configure time,
a warning will be generated and the manual page wont be
generated nor installed.
Man pages are not needed on target and the build step fails in certain
setups, so disable it.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
package/luksmeta/luksmeta.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/luksmeta/luksmeta.mk b/package/luksmeta/luksmeta.mk
index c8a19ddeeb..129713aec8 100644
--- a/package/luksmeta/luksmeta.mk
+++ b/package/luksmeta/luksmeta.mk
@@ -10,6 +10,7 @@ LUKSMETA_SITE = https://github.com/latchset/luksmeta/releases/download/v$(LUKSME
LUKSMETA_LICENSE = LGPL-2.1+
LUKSMETA_LICENSE_FILES = COPYING
LUKSMETA_DEPENDENCIES = host-pkgconf cryptsetup
+LUKSMETA_CONF_ENV = ac_cv_prog_A2X=""
LUKSMETA_INSTALL_STAGING = YES
$(eval $(autotools-package))
--
2.20.1
next reply other threads:[~2019-09-16 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 13:50 Peter Korsgaard [this message]
2019-09-17 20:50 ` [Buildroot] [PATCH] package/luksmeta: do not build man pages Thomas Petazzoni
2019-09-25 16:05 ` 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=20190916135048.5459-1-peter@korsgaard.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox