summaryrefslogtreecommitdiffstats
path: root/documentation/yocto-project-qs/yocto-project-qs.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/yocto-project-qs/yocto-project-qs.xml')
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml70
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 @@
566 <note> 566 <note>
567 Depending on the number of processors and cores, the 567 Depending on the number of processors and cores, the
568 amount of RAM, the speed of your Internet connection 568 amount of RAM, the speed of your Internet connection
569 and other factors, the build process could take several 569 and other factors, the build process could take
570 hours the first time you run it. 570 several hours the first time you run it.
571 Subsequent builds run much faster since parts of the 571 Subsequent builds run much faster since parts of the
572 build are cached. 572 build are cached.
573 </note> 573 </note>
574 <literallayout class='monospaced'> 574 <literallayout class='monospaced'>
575 $ bitbake core-image-sato 575 $ bitbake core-image-sato
576 </literallayout> 576 </literallayout>
577 <note>
578 <para>
579 If you experience a build error due to resources
580 temporarily being unavailable and it appears you
581 should not be having this issue, it might be due
582 to the combination of a 4.3+ Linux kernel and
583 <filename>systemd</filename> version 228+
584 (i.e. see this
585 <ulink url='http://unix.stackexchange.com/questions/253903/creating-threads-fails-with-resource-temporarily-unavailable-with-4-3-kernel'>link</ulink>
586 for information).
587 </para>
588
589 <para>
590 To work around this issue, you can try either
591 of the following:
592 <itemizedlist>
593 <listitem><para>
594 Try the build again.
595 </para></listitem>
596 <listitem><para>
597 Modify the "DefaultTasksMax"
598 <filename>systemd</filename> parameter
599 by uncommenting it and setting it to
600 "infinity".
601 You can find this parameter in the
602 <filename>system.conf</filename> file
603 located in
604 <filename>/etc/systemd</filename>
605 on most systems.
606 </para></listitem>
607 </itemizedlist>
608 </para>
609 </note>
577 For information on using the 610 For information on using the
578 <filename>bitbake</filename> command, see the 611 <filename>bitbake</filename> command, see the
579 "<ulink url='&YOCTO_DOCS_REF_URL;#usingpoky-components-bitbake'>BitBake</ulink>" 612 "<ulink url='&YOCTO_DOCS_REF_URL;#usingpoky-components-bitbake'>BitBake</ulink>"
@@ -724,6 +757,39 @@
724 <literallayout class='monospaced'> 757 <literallayout class='monospaced'>
725 $ bitbake core-image-base 758 $ bitbake core-image-base
726 </literallayout> 759 </literallayout>
760 <note>
761 <para>
762 If you experience a build error due to resources
763 temporarily being unavailable and it appears you
764 should not be having this issue, it might be due
765 to the combination of a 4.3+ Linux kernel and
766 <filename>systemd</filename> version 228+
767 (i.e. see this
768 <ulink url='http://unix.stackexchange.com/questions/253903/creating-threads-fails-with-resource-temporarily-unavailable-with-4-3-kernel'>link</ulink>
769 for information).
770 </para>
771
772 <para>
773 To work around this issue, you can try either
774 of the following:
775 <itemizedlist>
776 <listitem><para>
777 Try the build again.
778 </para></listitem>
779 <listitem><para>
780 Modify the "DefaultTasksMax"
781 <filename>systemd</filename> parameter
782 by uncommenting it and setting it to
783 "infinity".
784 You can find this parameter in the
785 <filename>system.conf</filename> file
786 located in
787 <filename>/etc/systemd</filename>
788 on most systems.
789 </para></listitem>
790 </itemizedlist>
791 </para>
792 </note>
727 Once the build completes, the resulting console-only image 793 Once the build completes, the resulting console-only image
728 is located in the Build Directory here: 794 is located in the Build Directory here:
729 <literallayout class='monospaced'> 795 <literallayout class='monospaced'>