From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] using linux 2.4 headers AND python
Date: Thu, 02 Apr 2009 07:22:40 +0200 [thread overview]
Message-ID: <87ljqj634v.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090402002811.GA29488@cloud.net.au> (Hamish Moffatt's message of "Thu\, 2 Apr 2009 11\:28\:11 +1100")
>>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:
>> Will you fix it or should I?
Hamish> I will.
Hamish> The Python package needs a bit of work anyway. I am using 2.5
Hamish> in my tree (2.4 is in the repo). There should be a proper
Hamish> build for the host now that we have $(HOST_DIR) too.
Exactly. I had it on my todo list, but feel free to do it if you have
time for it, I don't normally use Python.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-04-02 5:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 22:40 [Buildroot] using linux 2.4 headers Tobias McNulty
2009-03-24 22:56 ` Peter Korsgaard
2009-03-25 3:57 ` [Buildroot] using linux 2.4 headers AND python Tobias McNulty
2009-03-25 15:35 ` Tobias McNulty
2009-03-25 23:26 ` Hamish Moffatt
2009-03-26 0:27 ` Tobias McNulty
2009-03-26 6:57 ` Peter Korsgaard
2009-04-02 0:28 ` Hamish Moffatt
2009-04-02 5:22 ` 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=87ljqj634v.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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