diff options
Diffstat (limited to 'documentation/yocto-project-qs/yocto-project-qs.xml')
| -rw-r--r-- | documentation/yocto-project-qs/yocto-project-qs.xml | 70 |
1 files changed, 68 insertions, 2 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index e2c33d2f50..c1d3bf5927 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml @@ -566,14 +566,47 @@ <note> Depending on the number of processors and cores, the amount of RAM, the speed of your Internet connection - and other factors, the build process could take several - hours the first time you run it. + and other factors, the build process could take + several hours the first time you run it. Subsequent builds run much faster since parts of the build are cached. </note> <literallayout class='monospaced'> $ bitbake core-image-sato </literallayout> + <note> + <para> + If you experience a build error due to resources + temporarily being unavailable and it appears you + should not be having this issue, it might be due + to the combination of a 4.3+ Linux kernel and + <filename>systemd</filename> version 228+ + (i.e. see this + <ulink url='http://unix.stackexchange.com/questions/253903/creating-threads-fails-with-resource-temporarily-unavailable-with-4-3-kernel'>link</ulink> + for information). + </para> + + <para> + To work around this issue, you can try either + of the following: + <itemizedlist> + <listitem><para> + Try the build again. + </para></listitem> + <listitem><para> + Modify the "DefaultTasksMax" + <filename>systemd</filename> parameter + by uncommenting it and setting it to + "infinity". + You can find this parameter in the + <filename>system.conf</filename> file + located in + <filename>/etc/systemd</filename> + on most systems. + </para></listitem> + </itemizedlist> + </para> + </note> For information on using the <filename>bitbake</filename> command, see the "<ulink url='&YOCTO_DOCS_REF_URL;#usingpoky-components-bitbake'>BitBake</ulink>" @@ -724,6 +757,39 @@ <literallayout class='monospaced'> $ bitbake core-image-base </literallayout> + <note> + <para> + If you experience a build error due to resources + temporarily being unavailable and it appears you + should not be having this issue, it might be due + to the combination of a 4.3+ Linux kernel and + <filename>systemd</filename> version 228+ + (i.e. see this + <ulink url='http://unix.stackexchange.com/questions/253903/creating-threads-fails-with-resource-temporarily-unavailable-with-4-3-kernel'>link</ulink> + for information). + </para> + + <para> + To work around this issue, you can try either + of the following: + <itemizedlist> + <listitem><para> + Try the build again. + </para></listitem> + <listitem><para> + Modify the "DefaultTasksMax" + <filename>systemd</filename> parameter + by uncommenting it and setting it to + "infinity". + You can find this parameter in the + <filename>system.conf</filename> file + located in + <filename>/etc/systemd</filename> + on most systems. + </para></listitem> + </itemizedlist> + </para> + </note> Once the build completes, the resulting console-only image is located in the Build Directory here: <literallayout class='monospaced'> |