From: Peter Korsgaard <peter@korsgaard.com>
To: "Raphaël Mélotte" <raphael.melotte@mind.be>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-pymupdf: add missing host swig dependency
Date: Tue, 13 Jun 2023 14:47:59 +0200 [thread overview]
Message-ID: <87mt13wmtc.fsf@48ers.dk> (raw)
In-Reply-To: <20230420144537.2660650-1-raphael.melotte@mind.be> ("Raphaël Mélotte"'s message of "Thu, 20 Apr 2023 16:45:35 +0200")
>>>>> "Raphaël" == Raphaël Mélotte <raphael.melotte@mind.be> writes:
> It appears that python-pymupdf needs swig when building since mupdf
> was bumped to 1.18.0 in commit
> f00da714a20a7826dda67d66f2a6b6ef858ef3e3. This was not noticed before
> because when building on a machine where swig is already available
> outside buildroot, it is used and the build succeeds.
> This fixes the following build failure:
> swigging fitz/fitz.i to fitz/fitz_wrap.c
> swig -python -w509 -o fitz/fitz_wrap.c fitz/fitz.i
> error: command 'swig' failed: No such file or directory
> make: *** [package/pkg-generic.mk:293:
> /home/buildroot/autobuild/instance-2/output-1/build/python-pymupdf-1.21.1/.stamp_built]
> Error 1
> Fixes:
> - http://autobuild.buildroot.net/results/c689a385d984b87b63f3f2ff30338049774b1bf2
> - http://autobuild.buildroot.net/results/cf268d3631330a8288fb8ad2af009abb7f1ca6b0
> Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>
Committed to 2023.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-06-13 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 14:45 [Buildroot] [PATCH 1/1] package/python-pymupdf: add missing host swig dependency Raphaël Mélotte
2023-05-13 19:49 ` Yann E. MORIN
2023-06-13 12:47 ` Peter Korsgaard [this message]
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=87mt13wmtc.fsf@48ers.dk \
--to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox