From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python: fix to ensure libpython is stripped
Date: Fri, 14 Feb 2014 09:17:59 +0100 [thread overview]
Message-ID: <20140214091759.08e6d83c@skate> (raw)
In-Reply-To: <006301cf291a$d2064af0$7612e0d0$@calyptech.com>
Dear Przemyslaw Wrzos,
On Fri, 14 Feb 2014 11:22:18 +1100, Przemyslaw Wrzos wrote:
> > On Thu, 23 Jan 2014 14:40:38 +1100, Przemyslaw Wrzos wrote:
> >> The python and python3 builds mark libpython as read-only which
> >> prevents it from being stripped out correctly for the target.
> >>
> >> Signed-off-by: Przemyslaw Wrzos <przemyslaw.wrzos@calyptech.com>
> >
> > I have integrated this patch into the large set of Python patches I've
> > posted at
> > http://lists.busybox.net/pipermail/buildroot/2014-February/089309.html.
> >
> > However, I agree with Thomas De Schampheleire that this specific patch
> > should be merged for 2014.02, as it fixes a real problem, and gives a
> > nice size reduction.
> >
> > Thomas
>
> That makes sense. I assume you don't need anything from me at this point.
Nope, at this point your patch is in the queue, it should be handled at
some point :-)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-02-14 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 3:40 [Buildroot] [PATCH] python: fix to ensure libpython is stripped Przemyslaw Wrzos
2014-01-23 14:06 ` Thomas De Schampheleire
2014-01-23 23:53 ` Przemyslaw Wrzos
2014-01-27 20:05 ` Thomas De Schampheleire
2014-02-13 21:08 ` Thomas Petazzoni
2014-02-14 0:22 ` Przemyslaw Wrzos
2014-02-14 8:17 ` Thomas Petazzoni [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=20140214091759.08e6d83c@skate \
--to=thomas.petazzoni@free-electrons.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