From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] qemu: add support for python3
Date: Thu, 6 Sep 2018 09:50:48 +0200 [thread overview]
Message-ID: <20180906095048.44a886a1@windsurf> (raw)
In-Reply-To: <87bm9bdeg3.fsf@tkos.co.il>
Hello,
+Hollis, Matt.
On Wed, 05 Sep 2018 20:47:08 +0300, Baruch Siach wrote:
> Adam Duskett writes:
> > How would I test this? I am used to having BuildRoot handle the paths
> > for such dependencies.
>
> Just send RFC patch that you tested on your host with whatever Python
> version you have installed. There are a number of participants in this
> list that have access to hosts running RHEL6 or its derivatives.
It would actually be useful if Hollis (or Matt ?) could provide a
Docker container to easily access a RHEL6.5 system, so that people can
try out what happens on such an old system. I guess RHEL6.5 itself is
not easy to access because it's only for Redhat customers, but perhaps
there is an equivalent version of CentOS that would do the job ?
https://hub.docker.com/_/centos/ has a CentOS 6.6 docker image, but not
CentOS 6.5. However, CentOS 6.6 also has Python 2.6 by default:
$ sudo docker run -i -t centos:6.6 /bin/bash
[...]
[root at f7e0f2f6d7af /]# python
Python 2.6.6 (r266:84292, Jan 22 2014, 09:42:36)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-06 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 18:39 [Buildroot] [PATCH v2 1/1] qemu: add support for python3 Adam Duskett
2018-09-04 18:47 ` Baruch Siach
2018-09-04 19:09 ` Adam Duskett
2018-09-05 3:59 ` Baruch Siach
2018-09-05 16:43 ` Adam Duskett
2018-09-05 17:47 ` Baruch Siach
2018-09-06 7:50 ` Thomas Petazzoni [this message]
2018-09-06 22:58 ` Hollis Blanchard
2018-09-06 19:32 ` Thomas Petazzoni
2018-09-10 18:35 ` Trent Piepho
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=20180906095048.44a886a1@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