From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] more python enhancements
Date: Sat, 19 Jan 2008 01:18:05 +1100 [thread overview]
Message-ID: <20080118141805.GA8308@cloud.net.au> (raw)
In-Reply-To: <4790A58E.8030009@promwad.com>
On Fri, Jan 18, 2008 at 03:11:42PM +0200, Ivan Kuten wrote:
> Hamish Moffatt wrote:
> > Here's another improvement to the Python package.
> >
> > 1. Don't install the development headers, tools and static library into
> > the target system unless new configuration item is enabled.
> >
> > 2. Always install the development headers etc into the staging_dir, so
> > they can be used to build extension modules.
>
> please supply correct patch (svn diff or diff -urN)
>
> --- python.mk (.../mirror/buildroot/package/python) (revision 3461)
> +++ python.mk (.../beethoven/elara/trunk/buildroot/package/python) (revision 3461)
>
> I do not know how to apply it.
Oh sorry. The attached should do; I edited it by hand to add full paths.
Alternative you could apply it within the package/python directory using
"patch -p0 < br-python2.patch".
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: br-python2.patch
Type: text/x-diff
Size: 2793 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080119/0cde40c3/attachment.bin
prev parent reply other threads:[~2008-01-18 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 2:57 [Buildroot] [PATCH] more python enhancements Hamish Moffatt
2008-01-18 12:37 ` Bernhard Fischer
2008-01-21 0:10 ` Hamish Moffatt
2008-01-23 22:48 ` Hamish Moffatt
2008-01-18 13:11 ` Ivan Kuten
2008-01-18 14:18 ` Hamish Moffatt [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=20080118141805.GA8308@cloud.net.au \
--to=hamish@cloud.net.au \
--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