From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/scons: remove python from SCONS
Date: Sun, 31 Mar 2019 15:10:31 +0200 [thread overview]
Message-ID: <20190331151031.1ea749cb@windsurf> (raw)
In-Reply-To: <CAPi7W80cGNfGwAoZ-Zxw4jTy4qeSx+xENNQQ+qH7jzmb439J4A@mail.gmail.com>
On Sun, 31 Mar 2019 14:39:40 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> > Hm, don't we have a problem when BR2_PACKAGE_PYTHON3=y ? In this case,
> > scons being a host-python-package, it will be installed for
> > host-python3, i.e in /usr/lib/python3/.../, so how can it then work to
> > call it using python2 ?
> I tested it with the defconfig from the alljoyn autobuild falures
> (which have BR2_PACKAGE_PYTHON3=y) and it works because scons script
> is installed in $(HOST_DIR)/bin/scons and scons libraries are
> installed in $(HOST_DIR)/lib/scons-$(SCONS_VERSION) because we pass
> this path through --install-lib in scons.mk.
Hm, OK, so it means that running scons with python3 works even if it
has been installed for python2. Interesting.
I'm not sure what to do here. We could pick your patch as-is and rely
on this interesting behavior.
Or introduce two versions of scons, one for each python version, like
we did for python-setuptools. I'm not sure.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-31 13:10 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 [this message]
2019-04-01 20:47 ` 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=20190331151031.1ea749cb@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