From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] python: workaround distutils issue with binary extensions
Date: Tue, 14 Feb 2012 11:03:21 +0100 [thread overview]
Message-ID: <4F3A3169.9080109@visionsystems.de> (raw)
In-Reply-To: <20120214095225.A3DBC90A9D@busybox.osuosl.org>
Am 14.02.2012 10:32, schrieb Peter Korsgaard:
> commit: http://git.buildroot.net/buildroot/commit/?id=40281284ad5ab41fea4058d57c130cbae0fb9d70
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> distutils adds -L$LIBDIR (/usr/lib), breaking build of binary extensions.
> Seen with netifaces, but other extensions may be affected as well.
I hope this talk will change the situation in the future: https://us.pycon.org/2012/schedule/presentation/11/.
I've tried to raise this issue in distutils mailing list, but no one answered: http://python.6.n6.nabble.com/RFC-real-cross-compiling-support-for-Distutils2-td4368968.html
Peter, have you tried to make the following python patches upstream?
python-2.7-100-optional-test-modules.patch
python-2.7-101-optional-pydoc.patch
python-2.7-102-optional-2to3.patch
python-2.7-103-optional-sqlite.patch
python-2.7-104-optional-tk.patch
python-2.7-105-optional-curses.patch
python-2.7-106-optional-expat.patch
python-2.7-107-optional-codecs-cjk.patch
python-2.7-108-optional-nis.patch
python-2.7-109-optional-unicodedata.patch
python-2.7-110-optional-db.patch
python-2.7-111-optional-ssl.patch
python-2.7-112-optional-bzip2.patch
python-2.7-113-optional-zlib.patch
Yegor
next prev parent reply other threads:[~2012-02-14 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 9:32 [Buildroot] [git commit] python: workaround distutils issue with binary extensions Peter Korsgaard
2012-02-14 10:03 ` Yegor Yefremov [this message]
2012-02-14 11:27 ` Peter Korsgaard
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=4F3A3169.9080109@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--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