From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Asaf Kahlon <asafka7@gmail.com>
Cc: "Raphaël Mélotte" <raphael.melotte@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-pymupdf: depend on python3
Date: Fri, 13 Aug 2021 15:04:16 +0200 [thread overview]
Message-ID: <20210813150416.021d688a@windsurf> (raw)
In-Reply-To: <20210813073634.389426-1-asafka7@gmail.com>
On Fri, 13 Aug 2021 10:36:34 +0300
Asaf Kahlon <asafka7@gmail.com> wrote:
> According to the package documentation, python 3.6 or newer
> is needed.
>
> Fixes:
> - http://autobuild.buildroot.net/results/f857986b8c9b6d4a843f3694cae8527760540ed0/
>
> Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
> ---
> package/python-pymupdf/Config.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/python-pymupdf/Config.in b/package/python-pymupdf/Config.in
> index 54714eb3bf..64a81895ea 100644
> --- a/package/python-pymupdf/Config.in
> +++ b/package/python-pymupdf/Config.in
> @@ -4,6 +4,7 @@ config BR2_PACKAGE_PYTHON_PYMUPDF
> depends on BR2_TOOLCHAIN_HAS_SYNC_4 # mupdf -> harfbuzz
> depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_8 # mupdf -> harfbuzz
> depends on BR2_PACKAGE_XORG7
> + depends on BR2_PACKAGE_PYTHON3
This dependency should have been propagated to the two Config.in
comments in that file, so that they don't appear if Python3 is not
used. I fixed that up and applied to master. Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-13 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 7:36 [Buildroot] [PATCH 1/1] package/python-pymupdf: depend on python3 Asaf Kahlon
2021-08-13 13:04 ` Thomas Petazzoni [this message]
2021-08-14 6:04 ` Asaf Kahlon
2021-08-14 13:49 ` 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=20210813150416.021d688a@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=raphael.melotte@mind.be \
/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.