From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Python standard library files missing from rootfs
Date: Thu, 9 Jun 2016 17:40:13 +0200 [thread overview]
Message-ID: <20160609174013.7dc5f2ce@free-electrons.com> (raw)
In-Reply-To: <575986FC.9040307@etictelecom.com>
Hello,
On Thu, 9 Jun 2016 17:10:52 +0200, Mickael Chazaux wrote:
> On 09/06/2016 15:35, Mickael Chazaux wrote:
> > Hi,
> >
> >
> > all the standard library files are missing, including site.py.
>
> Sorry for the noise ^^ One of my packages does that in its makefile :
> find $(DESTDIR) -name *.py -exec rm {} \;
> find $(DESTDIR) -name *.pyc -exec rm {} \;
> find $(DESTDIR) -name *.pyo -exec chmod +x {} \;
>
> In OpenEmbedded it causes no harm, but in buildroot, it causes every .py{c} to disappear
It would be good if you had provided a bit more context here.
But I guess the reason is because we remove *.pyo files in Buildroot,
so if you remove *.py, *.pyc in your package, and Buildroot removes
*.pyo, there's nothing left.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-06-09 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 13:35 [Buildroot] Python standard library files missing from rootfs Mickael Chazaux
2016-06-09 15:10 ` Mickael Chazaux
2016-06-09 15:40 ` 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=20160609174013.7dc5f2ce@free-electrons.com \
--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