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: Fri, 03 May 2019 14:08:34 +0000 [thread overview]
Message-ID: <bug-11831-163-gD8H2tQeaj@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 #6 from Tibor Stolz <tistolz@outlook.de> ---
The build log for python-cantools in detail:
>>> python-cantools 18.0.1 Downloading
cantools-18.0.1.tar.gz: OK (sha256:
dc5d265103b8b11d4c7cc21996ad1954325b1f1930837505cabb0b5b137d37ee)
>>> python-cantools 18.0.1 Extracting
gzip -d -c
/home/tibor/Buildroot/buildroot-2019.02.2/dl/python-cantools/cantools-18.0.1.tar.gz
| tar --strip-components=1 -C
/home/tibor/Buildroot/buildroot-2019.02.2/output/build/python-cantools-18.0.1
-xf -
>>> python-cantools 18.0.1 Patching
>>> python-cantools 18.0.1 Configuring
>>> python-cantools 18.0.1 Building
(cd
/home/tibor/Buildroot/buildroot-2019.02.2/output/build/python-cantools-18.0.1//;
_PYTHON_SYSCONFIGDATA_NAME="_sysconfigdata_m_linux_arm-linux-gnueabihf"
PATH="/home/tibor/Buildroot/buildroot-2019.02.2/output/host/bin:/home/tibor/Buildroot/buildroot-2019.02.2/output/host/sbin:/home/tibor/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
PYTHONPATH="/home/tibor/Buildroot/buildroot-2019.02.2/output/target/usr/lib/python3.7/"
PYTHONNOUSERSITE=1
_python_sysroot=/home/tibor/Buildroot/buildroot-2019.02.2/output/host/arm-buildroot-linux-uclibcgnueabihf/sysroot
_python_prefix=/usr _python_exec_prefix=/usr
/home/tibor/Buildroot/buildroot-2019.02.2/output/host/bin/python setup.py build
)
Traceback (most recent call last):
File "setup.py", line 4, in <module>
import cantools
File
"/home/tibor/Buildroot/buildroot-2019.02.2/output/build/python-cantools-18.0.1/cantools/__init__.py",
line 6, in <module>
from . import db
File
"/home/tibor/Buildroot/buildroot-2019.02.2/output/build/python-cantools-18.0.1/cantools/db/__init__.py",
line 4, in <module>
from .database import Database
File
"/home/tibor/Buildroot/buildroot-2019.02.2/output/build/python-cantools-18.0.1/cantools/db/database.py",
line 3, in <module>
from .formats import dbc
File
"/home/tibor/Buildroot/buildroot-2019.02.2/output/build/python-cantools-18.0.1/cantools/db/formats/dbc.py",
line 4, in <module>
from pyparsing import Word
ModuleNotFoundError: No module named 'pyparsing'
package/pkg-generic.mk:238: recipe for target
'/home/tibor/Buildroot/buildroot-2019.02.2/output/build/python-cantools-18.0.1/.stamp_built'
failed
make[1]: ***
[/home/tibor/Buildroot/buildroot-2019.02.2/output/build/python-cantools-18.0.1/.stamp_built]
Error 1
Makefile:84: recipe for target '_all' failed
make: *** [_all] Error 2
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-05-03 14:08 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 [this message]
2019-05-07 14:59 ` bugzilla at busybox.net
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-gD8H2tQeaj@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