[yocto] [zeus] icu-native-64.2-r0 do_configure: configure failed

star at gmx.li star at gmx.li
Tue Oct 29 23:25:09 PDT 2019


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


More information about the yocto mailing list