All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2016-09-05
Date: Thu, 08 Sep 2016 11:43:01 +0200	[thread overview]
Message-ID: <87vay67mmy.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAFOYHZA8sdf7ZFA-CKKSngLUrbKAj16xsswJ64r+JGgCUKjz9g@mail.gmail.com> (Chris Packham's message of "Thu, 8 Sep 2016 20:07:43 +1200")

>>>>> "Chris" == Chris Packham <judge.packham@gmail.com> writes:

Hi,

 >> The line QSTRING_BLACK_LIST = {'NULL', 'number_of', } is defining a
 >> set. It works in Python 2.7, but not in Python 2.6. I guess replacing
 >> with:
 >> 
 >> QSTRING_BLACK_LIST = set(['NULL', 'number_of'])
 >> 
 >> should work fine (tested with 2.6, 2.7 and 3.5)

 > So before I go down that path. Are we saying python >2.6 is required
 > for buildroot? Or at least that is the expectation for the
 > auto-builders.

Yes - From docs/manual/prerequisite.txt:

=== Mandatory packages

* Build tools:
..
** +python+ (version 2.6 or any later)

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2016-09-08  9:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160906063035.18941102741@stock.ovh.net>
2016-09-07  9:13 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2016-09-05 Chris Packham
2016-09-07  9:21   ` Yann E. MORIN
2016-09-07  9:44     ` Thomas Petazzoni
2016-09-07  9:28   ` Thomas Petazzoni
2016-09-08  8:07     ` Chris Packham
2016-09-08  9:43       ` Peter Korsgaard [this message]
2016-09-08 10:07         ` Chris Packham
     [not found] <20160906063034.C474D1028BB@stock.ovh.net>
2016-09-10 13:27 ` Romain Naour
     [not found]   ` <20160910135635.GH6777@waldemar-brodkorb.de>
2016-09-10 15:45     ` Romain Naour
     [not found]       ` <9a18dc1c-25bd-0925-1a78-dc7a5612d465@gmail.com>
     [not found]         ` <20160911133437.GI6777@waldemar-brodkorb.de>
2016-09-13  6:56           ` Romain Naour
2016-11-05 17:12             ` Romain Naour
2016-11-05 17:17               ` Waldemar Brodkorb
2016-11-05 18:57                 ` Romain Naour

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=87vay67mmy.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.