Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mickael Chazaux <mickael.chazaux@etictelecom.com>
To: buildroot@busybox.net
Subject: [Buildroot] Python standard library files missing from rootfs
Date: Thu, 9 Jun 2016 17:10:52 +0200	[thread overview]
Message-ID: <575986FC.9040307@etictelecom.com> (raw)
In-Reply-To: <575970BA.7080407@etictelecom.com>

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


-- 
Mickael Chazaux
Software Engineer
Tel : (33) 476 042 009
Fax : (33) 476 042 001

ETIC TELECOM
13, Chemin du Vieux Ch?ne
38240 MEYLAN
Tel: 33 4 76 04 20 00
fax : 33 4 76 04 20 01

  reply	other threads:[~2016-06-09 15:10 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 [this message]
2016-06-09 15:40   ` 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=575986FC.9040307@etictelecom.com \
    --to=mickael.chazaux@etictelecom.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