Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] more python enhancements
Date: Fri, 18 Jan 2008 15:11:42 +0200	[thread overview]
Message-ID: <4790A58E.8030009@promwad.com> (raw)
In-Reply-To: <20080118025745.GA30978@cloud.net.au>

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.
> 
> 
> Hamish
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot

Hi,

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.



Regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

  parent reply	other threads:[~2008-01-18 13:11 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 [this message]
2008-01-18 14:18   ` Hamish Moffatt

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=4790A58E.8030009@promwad.com \
    --to=ivan.kuten@promwad.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