Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: swirsky at gmail.com <swirsky@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Missing .pyc files in target filesystem
Date: Mon, 12 Apr 2021 12:08:00 -0700	[thread overview]
Message-ID: <003801d72fcf$28780910$79681b30$@gmail.com> (raw)

We're not getting python .pyc files for the Python packages in the target
filesystem /usr/lib/python3.8/ and I can't figure out why, despite several
days of looking at this.

 

We're on Buildroot 2020.02.03 and I've tried both

 

        BR2_PACKAGE_PYTHON_PYC_ONLY=y

 

        BR2_PACKAGE_PYTHON_PY_PYC=y

 

in the config. I only see .py files.

 

Any ideas on how to debug this? What's the thing in buildroot that creates
the .pyc files?

 

Thanks!

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210412/f739d2a2/attachment.html>

             reply	other threads:[~2021-04-12 19:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 19:08 swirsky at gmail.com [this message]
2021-04-12 19:50 ` [Buildroot] Missing .pyc files in target filesystem Arnout Vandecappelle
2021-04-12 19:54   ` swirsky at gmail.com
2021-04-12 20:22     ` Arnout Vandecappelle
2021-04-14  2:24       ` swirsky at gmail.com

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='003801d72fcf$28780910$79681b30$@gmail.com' \
    --to=swirsky@gmail.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