From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] python: workaround distutils issue with binary extensions
Date: Tue, 14 Feb 2012 12:27:29 +0100 [thread overview]
Message-ID: <8762f9wt7i.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4F3A3169.9080109@visionsystems.de> (Yegor Yefremov's message of "Tue, 14 Feb 2012 11:03:21 +0100")
>>>>> "Yegor" == Yegor Yefremov <yegor_sub1@visionsystems.de> writes:
Hi,
Yegor> I hope this talk will change the situation in the future: https://us.pycon.org/2012/schedule/presentation/11/.
Yes, let's hope so.
Yegor> I've tried to raise this issue in distutils mailing list, but no
Yegor> one answered:
Yegor> http://python.6.n6.nabble.com/RFC-real-cross-compiling-support-for-Distutils2-td4368968.html
Thanks.
Yegor> Peter, have you tried to make the following python patches upstream?
No, I haven't. I'm not the author of them (Thomas did - I think he based
them on patches in openwrt).
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-02-14 11:27 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
2012-02-14 11:27 ` Peter Korsgaard [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=8762f9wt7i.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--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