Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Issue adding subprocess32 python package to buildroot
Date: Sat, 9 Sep 2017 20:53:59 +0200	[thread overview]
Message-ID: <20170909205359.2346ba4e@windsurf.lan> (raw)
In-Reply-To: <20170909161401.GC2850@scaer>

Hello,

On Sat, 9 Sep 2017 18:14:01 +0200, Yann E. MORIN wrote:

> On 2017-09-08 15:18 +0100, Paul Gildea spake thusly:
> > I am trying to install subprocess32 with my python 2.7 installation via
> > buildroot. It's an older version of buildroot and doesn't have
> > python-package,  
> 
> python-package was introduced in December 2013, so appeared in Buildroot
> 2014.02. This means you are using  version that is almost 4 years old
> now.
> 
> And below, we can see that you are using the GENTARGETS infrastructure.
> This was removed in July 2012, now more than 5 years ago...
> 
> We can't help on such an old version.
> 
> I would suggest that you upgrade to at least our first LTS version,
> 2017.02, or to the latest release, 2017.08.

I already replied exactly the same thing, to the same person, asking
the same question on Stack Overflow:
https://stackoverflow.com/questions/46079968/issue-importing-subprocess32.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-09-09 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08 14:18 [Buildroot] Issue adding subprocess32 python package to buildroot Paul Gildea
2017-09-09 16:14 ` Yann E. MORIN
2017-09-09 18:53   ` Thomas Petazzoni [this message]
2017-09-09 19:03   ` Paul Gildea
2017-09-11 23:07 ` Arnout Vandecappelle
2017-09-14 15:22   ` Paul Gildea

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=20170909205359.2346ba4e@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.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