Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Przemyslaw Wrzos <przemyslaw.wrzos@calyptech.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python: fix to ensure libpython is stripped
Date: Fri, 24 Jan 2014 10:53:19 +1100	[thread overview]
Message-ID: <002801cf1896$4acddc40$e06994c0$@calyptech.com> (raw)
In-Reply-To: <CAAXf6LV1vHUAEDGdCmMZ0nC-XX3x9QSZOWnAZbNS=rG=0bGnFA@mail.gmail.com>

Hello Thomas,

On Fri, 24 Jan 2014 at 01:06:08, Thomas De Schampheleire wrote:

> On Thu, Jan 23, 2014 at 4:40 AM, Przemyslaw Wrzos
> <przemyslaw.wrzos@calyptech.com> 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>
>> ---
>
> Acked-by: Thomas De Schampheleire
> <thomas.de_schampheleire@alcatel-lucent.com> Tested-by: Thomas De
> Schampheleire <thomas.de_schampheleire@alcatel-lucent.com> (tested with
> python2 only)
> 
> Note: the library will remain writable, but this doesn't look like a
> big problem to me...
> 
> By the way: nice find! Saves about 4MB on Python 2!

Yep, that's the only caveat without stuffing some horrible hack into
buildroot elsewhere to get around it. I couldn't think of a downside
though, and I've been running this on my embedded systems for a year now
without issue.

Cheers,
Przemyslaw Wrzos

  reply	other threads:[~2014-01-23 23:53 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 [this message]
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

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='002801cf1896$4acddc40$e06994c0$@calyptech.com' \
    --to=przemyslaw.wrzos@calyptech.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