From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/scons: remove python from SCONS
Date: Mon, 1 Apr 2019 22:47:16 +0200 [thread overview]
Message-ID: <20190401224716.50287285@windsurf> (raw)
In-Reply-To: <20190331121810.28608-1-fontaine.fabrice@gmail.com>
On Sun, 31 Mar 2019 14:18:10 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Remove $(HOST_DIR)/bin/python from SCONS variable to allow each scons
> package to select their python interpreter. Indeed, most of the scons
> packages (alljoyn, benejson, gpsd) only supports python2
>
> Fixes:
> - http://autobuild.buildroot.org/results/b45f9fb69615b80758adeff4571e170c3bd9356b
> - http://autobuild.buildroot.org/results/13144a7ebd64ef7889312053f06a14047eea232d
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/alljoyn-base/alljoyn-base.mk | 4 ++--
> package/alljoyn-tcl-base/alljoyn-tcl-base.mk | 4 ++--
> package/alljoyn-tcl/alljoyn-tcl.mk | 4 ++--
> package/alljoyn/alljoyn.mk | 4 ++--
> package/benejson/benejson.mk | 4 ++--
> package/gpsd/gpsd.mk | 10 +++++-----
> package/mongodb/mongodb.mk | 4 ++--
> package/scons/scons.mk | 2 +-
> 8 files changed, 18 insertions(+), 18 deletions(-)
I don't know if it is the best/right solution, but it does the job for
now, so let's use this for the moment. We can always revisit the SCons
integration later if needed.
Applied to mater, thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-04-01 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 12:18 [Buildroot] [PATCH 1/1] package/scons: remove python from SCONS Fabrice Fontaine
2019-03-31 12:25 ` Thomas Petazzoni
2019-03-31 12:39 ` Fabrice Fontaine
2019-03-31 13:10 ` Thomas Petazzoni
2019-04-01 20:47 ` Thomas Petazzoni [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=20190401224716.50287285@windsurf \
--to=thomas.petazzoni@bootlin.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