Winston.huang: Created page with "{{DISPLAYTITLE:x86 Yocto BSP FAQ}}
TOC
==..."

2021-05-27T02:34:53Z

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> ==..."

New page

{{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>
== <span style="color:#0070c0">bitbake failed</span> ==

=== 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.
::<code>$ bitbake -k clang</code>
::or
::<code>$ bitbake -k qtwebkit</code>

*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
::<code>$ grep "BB_NUMBER_THREADS" conf/local.conf | sed "s/.*\"$.*$\"$/\1/"</code>
:set new number of threads
::<code>$ sed -i "s/BB_NUMBER_THREADS.*/BB_NUMBER_THREADS = \"<span style="color:#ff0000">${THREADS}</span>\"/" conf/local.conf</code>
:(remember to replace the <span style="color:#ff0000">'''${THREADS}'''</span> with the appropriate one)

=== make error ===

==== Solution ====

*clean the failed one, then re-build it individually

:<code>$ bitbake -k ${failed_package} -c clean</code>
:<code>$ bitbake -k ${failed_package}</code>

X86/Yocto BSP/FAQ - Revision history

Winston.huang: Created page with "{{DISPLAYTITLE:x86 Yocto BSP FAQ}} __TOC__ ==..."

Winston.huang: Created page with "{{DISPLAYTITLE:x86 Yocto BSP FAQ}}
TOC
==..."