x86 Yocto BSP FAQ

From ESS-WIKI
Revision as of 03:34, 27 May 2021 by Winston.huang (Talk | contribs) (Created page with "{{DISPLAYTITLE:x86 Yocto BSP FAQ}} <div style="float:right; position:fixed; margin:0 1em 0 0; top5100px; right:10px; max-height: 350px; overflow: auto">__TOC__</div> ==...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

bitbake failed

ninja: build stopped: subcommand failed

Cause

It usually happens on low performance host machine, and almost the qt* or clang* are the failed ones.

Solution

  • build the failed one individually
(It is recommended to use this way first.)
e.g.
$ bitbake -k clang
or
$ bitbake -k qtwebkit
  • decrease number of threads used for the parallel build.
(The less number of threads will take more time to finish the whole building process.)
get original nummber of threads
$ grep "BB_NUMBER_THREADS" conf/local.conf | sed "s/.*\"\(.*\)\"$/\1/"
set new number of threads
$ sed -i "s/BB_NUMBER_THREADS.*/BB_NUMBER_THREADS = \"${THREADS}\"/" conf/local.conf
(remember to replace the ${THREADS} with the appropriate one)

make error

Solution

  • clean the failed one, then re-build it individually
$ bitbake -k ${failed_package} -c clean
$ bitbake -k ${failed_package}