From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH 2/2] package/flashrom: disable documentation and man-pages
Date: Sun, 18 Aug 2024 23:56:26 +0200 [thread overview]
Message-ID: <20240818215627.1055491-2-thomas.petazzoni@bootlin.com> (raw)
In-Reply-To: <20240818215627.1055491-1-thomas.petazzoni@bootlin.com>
The build of the manpage currently fails with:
ERROR: File 'doc/man8' could not be found
FAILED: meson-internal__install
As we don't care about man pages and documentation in Buildroot, let's
disable them. The issue has nevertheless been reported at
https://github.com/flashrom/flashrom/issues/329.
Fixes:
http://autobuild.buildroot.net/results/885a957d1b5305d3b91339487cc2a0d64dc74f5e/
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
package/flashrom/flashrom.mk | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/package/flashrom/flashrom.mk b/package/flashrom/flashrom.mk
index 46d42640e9..8648965303 100644
--- a/package/flashrom/flashrom.mk
+++ b/package/flashrom/flashrom.mk
@@ -14,7 +14,9 @@ FLASHROM_CONF_OPTS = \
-Dich_descriptors_tool=enabled \
-Dtests=disabled \
-Duse_internal_dmi=true \
- -Dwerror=false
+ -Dwerror=false \
+ -Dman-pages=disabled \
+ -Ddocumentation=disabled
FLASHROM_PROGRAMMERS = \
buspirate_spi \
--
2.46.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-18 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 21:56 [Buildroot] [PATCH 1/2] package/flashrom: bump to final 1.4.0 release Thomas Petazzoni via buildroot
2024-08-18 21:56 ` Thomas Petazzoni via buildroot [this message]
2024-08-19 20:39 ` Yann E. MORIN
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=20240818215627.1055491-2-thomas.petazzoni@bootlin.com \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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.