From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11831] python-pyparsing: "No module named 'pyparsing'" on target / while building cantools
Date: Tue, 07 May 2019 14:59:05 +0000 [thread overview]
Message-ID: <bug-11831-163-eph6iJKquQ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11831-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11831
--- Comment #7 from Tibor Stolz <tistolz@outlook.de> ---
Created attachment 8026
--> https://bugs.busybox.net/attachment.cgi?id=8026&action=edit
python_ok_bbb_defconfig
I'm sorry I cannot repeat the problem anymore. Using exactly the same buildroot
version and menu settings (except "System hostname" and "System banner"), I get
packages python-pyparsing and python-spidev that work fine and can be imported
into a python3 session without any issue.
For your reference, I'm attaching the main config file, created using "make
savedefconfig".
I'm closing the bug until I hit that behaviour again. (I hope not...)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-05-07 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 13:52 [Buildroot] [Bug 11831] New: python-pyparsing: "No module named 'pyparsing'" on target / while building cantools bugzilla at busybox.net
2019-05-03 13:54 ` [Buildroot] [Bug 11831] " bugzilla at busybox.net
2019-05-03 13:54 ` bugzilla at busybox.net
2019-05-03 13:55 ` bugzilla at busybox.net
2019-05-03 13:58 ` bugzilla at busybox.net
2019-05-03 13:59 ` bugzilla at busybox.net
2019-05-03 14:08 ` bugzilla at busybox.net
2019-05-07 14:59 ` bugzilla at busybox.net [this message]
2019-05-07 15:00 ` bugzilla at busybox.net
2019-05-14 11:55 ` bugzilla at busybox.net
2019-05-14 12:04 ` bugzilla at busybox.net
2019-05-14 12:06 ` [Buildroot] [Bug 11831] python-pyparsing: "No module named 'pyparsing'" while building cantools (SOLVED: use host-python-pyparsing) bugzilla at busybox.net
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=bug-11831-163-eph6iJKquQ@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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