From: Asaf Kahlon <asafka7@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libsoup: needs host-python3
Date: Thu, 30 Aug 2018 13:14:30 +0300 [thread overview]
Message-ID: <20180830101430.14862-1-asafka7@gmail.com> (raw)
The tld-parser script in libsoup is now written in Python,
and needs python3 to run.
Fixes:
http://autobuild.buildroot.net/results/91c2d6a1ca011787130db06695d6cd9e882f7258
http://autobuild.buildroot.net/results/a318e595f02937534b3f8698ef4c04194a8b34af
Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
---
Maybe this specific script can run even with python2, but I don't think patchting the
"/usr/bin/env python3" line would be the right solution, especially considering
the fact that they already have python3-only code in recent commits.
---
package/libsoup/libsoup.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/libsoup/libsoup.mk b/package/libsoup/libsoup.mk
index 95bd682010..ef17f27fcd 100644
--- a/package/libsoup/libsoup.mk
+++ b/package/libsoup/libsoup.mk
@@ -14,7 +14,7 @@ LIBSOUP_INSTALL_STAGING = YES
LIBSOUP_CONF_ENV = ac_cv_path_GLIB_GENMARSHAL=$(LIBGLIB2_HOST_BINARY)
LIBSOUP_CONF_OPTS = --disable-glibtest --enable-vala=no --with-gssapi=no
LIBSOUP_DEPENDENCIES = host-pkgconf host-libglib2 \
- libglib2 libxml2 sqlite host-intltool
+ libglib2 libxml2 sqlite host-intltool host-python3
ifeq ($(BR2_PACKAGE_LIBSOUP_GNOME),y)
LIBSOUP_CONF_OPTS += --with-gnome
--
2.17.1
next reply other threads:[~2018-08-30 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 10:14 Asaf Kahlon [this message]
2018-08-30 15:10 ` [Buildroot] [PATCH 1/1] package/libsoup: needs host-python3 Thomas Petazzoni
2018-08-30 18:11 ` Baruch Siach
2018-08-30 18:51 ` Asaf Kahlon
2018-09-01 13:53 ` 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=20180830101430.14862-1-asafka7@gmail.com \
--to=asafka7@gmail.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