From: star@gmx.li
To: yocto@yoctoproject.org
Subject: [zeus] icu-native-64.2-r0 do_configure: configure failed
Date: Wed, 30 Oct 2019 07:25:09 +0100 [thread overview]
Message-ID: <trinity-8eddf10e-7c97-465a-a389-4a6462d8fdf7-1572416709913@3c-app-gmx-bs26> (raw)
Build of image failed, I got strange and long error messages like:
ERROR: icu-native-64.2-r0 do_configure: configure failed
ERROR: icu-native-64.2-r0 do_configure: Execution of '/home/.../tmp/work/x86_64-linux/icu-native/64.2-r0/temp/run.do_configure
...
| configure: WARNING: unrecognized options: --disable-silent-rules, --disable-dependency-tracking
| Not rebuilding data/rules.mk, assuming prebuilt data in data/in
| Spawning Python to generate test/testdata/rules.mk...
| Traceback (most recent call last):
| File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
| "__main__", mod_spec)
| File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
| exec(code, run_globals)
| File "/home/.../tmp/work/x86_64-linux/icu-native/64.2-r0/icu/source/data/buildtool/__main__.py", line 19, in <module>
| import BUILDRULES
| File "/home/.../tmp/work/x86_64-linux/icu-native/64.2-r0/icu/source/test/testdata/BUILDRULES.py", line 4, in <module>
| from distutils.sysconfig import parse_makefile
| ModuleNotFoundError: No module named 'distutils.sysconfig'
| configure: error: Python failed to run; see above error.
| WARNING: exit code 1 from a shell command.
|
ERROR: Task (virtual:native:/home/.../poky/meta/recipes-support/icu/icu_64.2.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1846 tasks of which 1819 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
virtual:native:/home/.../poky/meta/recipes-support/icu/icu_64.2.bb:do_configure
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
-----
The messages has been so strange (to me) - couldn't found the trigger for building that. Finally I bitbaked all my image packages manually and found that strace and valgrind triggers this icu-native. So I have two questions:
a) What goes wrong here and how can this be avoid?
b) How do I found which module is responsible. There is nothing about strace/valgrind mentioned in the log. I just had to build all my additional packets of my image manually to find the triggers for this icu-native.
Thank you
next reply other threads:[~2019-10-30 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 6:25 star [this message]
2019-10-30 10:30 ` [zeus] icu-native-64.2-r0 do_configure: configure failed Ross Burton
2019-10-30 12:11 ` Arno Steffens
2019-10-30 17:30 ` Ross Burton
2019-10-31 9:20 Arno Steffens
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=trinity-8eddf10e-7c97-465a-a389-4a6462d8fdf7-1572416709913@3c-app-gmx-bs26 \
--to=star@gmx.li \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.