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] Pushing cross-compilation fixes to upstream Python
Date: Fri, 10 Jan 2014 07:13:26 +0800	[thread overview]
Message-ID: <20140110071326.2e539507@skate> (raw)

Hello,

I've started updating Buildroot to use more recent versions of Python.
And at the same time, I'm trying to push the necessary
cross-compilation patches to upstream Python.

It turns out that Matthias Klose from Canonical has already done a
great job, and has pushed numerous cross-compilation fixes to Python.
Therefore, a lot less fixes are needed now.

I have submitted the following three bug reports that contain patches
to fix various cross-compilation issues:

  http://bugs.python.org/issue20211
  http://bugs.python.org/issue20212
  http://bugs.python.org/issue20213

I've also submitted some patches that add numerous --enable/--disable
options to the Python configure script to selectively enabled/disable
the build of certain Python modules or extensions. See:

  http://bugs.python.org/issue20210

It would be very useful if people working for other build systems than
Buildroot could take the time to test these patches, and support them
to ease their integration in upstream Python.

Note that these patches are against Python master, but they apply very
easily on 3.4.0b1.

Thanks,

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

                 reply	other threads:[~2014-01-09 23:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140110071326.2e539507@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