From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gpsd: fix Python 2.5 build failure
Date: Mon, 30 Jul 2012 19:16:52 +0200 [thread overview]
Message-ID: <20120730191652.562a15e2@skate> (raw)
In-Reply-To: <1343632101-7179-1-git-send-email-spdawson@gmail.com>
Le Mon, 30 Jul 2012 08:08:21 +0100,
spdawson at gmail.com a ?crit :
> From: Simon Dawson <spdawson@gmail.com>
>
> The platform.linux_distribution method was introduced in Python 2.6. Some
> of the Buildroot autobuilders still use Python 2.5, which is causing build
> failures such as the following.
>
> http://autobuild.buildroot.net/results/045f1f69bac170d8e75cb4952a2e5b4e85a677b8/build-end.log
>
> This patch removes the linux distribution check from the gpsd SConstruct file.
>
> Signed-off-by: Simon Dawson <spdawson@gmail.com>
Applied, thanks.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-07-30 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 7:08 [Buildroot] [PATCH] gpsd: fix Python 2.5 build failure spdawson at gmail.com
2012-07-30 17:16 ` 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=20120730191652.562a15e2@skate \
--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