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: Tue, 13 Apr 2021 19:24:16 -0700	[thread overview]
Message-ID: <00a401d730d5$455c8ea0$d015abe0$@gmail.com> (raw)
In-Reply-To: <de925ef6-7c7f-94ef-2c6f-57d40dcec656@mind.be>

I never did figure out the why, but I "binary searched" the past dozen or so commits and found the one that broke the .pyc files. It was when I added a certain external out-of-tree package to our project. 

What's interesting is 
  - this package was not specified in the standard  config file (ie., the files under configs that the menu manages). It was listed in the Config.in where all the external packages are enumerated. I was under the impression that packages not in a ~/project/configs configuration had no effect on the build
  - the package in question was "remote_pdb"

I thought that, maybe, someone put some code to see if you've turned on any form of pdb and suppresses .pyc generation but I saw no such thing when reading the source code. So my best guess is that I had a faulty makefile for this external project that was causing the rest of the python machinery to fail (perhaps none of the other "hooks" ran) and it failed without letting me know.

Thanks for all your help, Arnout!

      reply	other threads:[~2021-04-14  2:24 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
2021-04-12 20:22     ` Arnout Vandecappelle
2021-04-14  2:24       ` swirsky at gmail.com [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='00a401d730d5$455c8ea0$d015abe0$@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