From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patching python to 2.7 (Thomas Petazzoni)
Date: Tue, 4 Jan 2011 13:52:17 +0100 [thread overview]
Message-ID: <20110104135217.5092017b@surf> (raw)
In-Reply-To: <000001cbac0a$1ebf6020$5c3e2060$@com>
Hello Barry,
On Tue, 4 Jan 2011 12:22:57 -0000
"Barry Bridges" <barry@disignconsultants.com> wrote:
> It must be me doing something wrong. I've seen Maxime Ripards patches but
> for some reason can't get them to work.
>
> What version of BR would you recommend for the patches
I think 2010.11 should work, and the latest Git as well.
> and is it just a matter of adding the patches into the package/python directory?
No. You have to apply Maxime's patches to Buildroot. Maxime's patches
are not against Python itself, but against Buildroot.
Regards,
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:[~2011-01-04 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1294142401.15574.buildroot@busybox.net>
2011-01-04 12:22 ` [Buildroot] Patching python to 2.7 (Thomas Petazzoni) Barry Bridges
2011-01-04 12:52 ` 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=20110104135217.5092017b@surf \
--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