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:54:28 -0700 [thread overview]
Message-ID: <007101d72fd5$a67676c0$f3636440$@gmail.com> (raw)
In-Reply-To: <c7681c66-e513-380e-cba3-8b9b2f6b98fa@mind.be>
Thanks, Arnout. We were in fact using the symbols
BR2_PACKAGE_PYTHON3_PYC_ONLY
BR2_PACKAGE_PYTHON3_PY_PYC
When I typed it into my email, I left off the 3. I checked my config. The
last build I tried had
BR2_PACKAGE_PYTHON3_PYC_ONLY
And we got .py files in the target filesystem
-----Original Message-----
From: Arnout Vandecappelle <arnout@mind.be>
Sent: Monday, April 12, 2021 12:50 PM
To: swirsky at gmail.com; buildroot at busybox.net
Subject: Re: [Buildroot] Missing .pyc files in target filesystem
On 12/04/2021 21:08, swirsky at gmail.com wrote:
> 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
>
How did you generate this config? The symbols are
BR2_PACKAGE_PYTHON3_PYC_ONLY
BR2_PACKAGE_PYTHON3_PY_PYC
when you're using python3. Setting the python2 configuration will not affect
python3 - and in fact, those python2 symbols should be removed when any
kconfig target is run.
Regards,
Arnout
> ?
>
> 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!
>
> ?
>
> ?
>
> ?
>
> ?
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2021-04-12 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 19:08 [Buildroot] Missing .pyc files in target filesystem swirsky at gmail.com
2021-04-12 19:50 ` Arnout Vandecappelle
2021-04-12 19:54 ` swirsky at gmail.com [this message]
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='007101d72fd5$a67676c0$f3636440$@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