summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorNicolas Dechesne <nicolas.dechesne@linaro.org>2020-07-30 13:37:11 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-09-17 10:09:34 +0100
commit28afbf81ecb34add93f5eed2c1a41ec5f278d0a7 (patch)
tree62804dd25f10e4a3781268549cde2aba8bafcb03 /documentation
parent283ed72d487ed78d4f8e0fcc17f635d6c212b7c6 (diff)
downloadpoky-28afbf81ecb34add93f5eed2c1a41ec5f278d0a7.tar.gz
sphinx: fix links when the link text should be displayed
When an hyperlink should be display in the output, there is no need to any specific syntax or marker, the parser finds links and mail addresses in ordinary text. Somehow the conversion from pandoc generated wrong output in the form: ` <link>`__. This patch is generated using the following Python regexp: line = re.sub("` <(https?://.*)>`__", "\\1", line) (From yocto-docs rev: a35d735a74425dff34c63c086947624467658c40) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/adt-manual/adt-intro.rst10
-rw-r--r--documentation/adt-manual/adt-package.rst6
-rw-r--r--documentation/adt-manual/adt-prepare.rst4
-rw-r--r--documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst2
-rw-r--r--documentation/bsp-guide/bsp.rst6
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.rst30
-rw-r--r--documentation/dev-manual/dev-manual-start.rst6
-rw-r--r--documentation/kernel-dev/kernel-dev-common.rst2
-rw-r--r--documentation/kernel-dev/kernel-dev-concepts-appx.rst4
-rw-r--r--documentation/overview-manual/overview-manual-concepts.rst2
-rw-r--r--documentation/overview-manual/overview-manual-development-environment.rst4
-rw-r--r--documentation/ref-manual/faq.rst2
-rw-r--r--documentation/ref-manual/migration.rst16
-rw-r--r--documentation/ref-manual/ref-classes.rst2
-rw-r--r--documentation/ref-manual/ref-devtool-reference.rst2
-rw-r--r--documentation/ref-manual/ref-kickstart.rst2
-rw-r--r--documentation/ref-manual/ref-qa-checks.rst2
-rw-r--r--documentation/ref-manual/ref-release-process.rst4
-rw-r--r--documentation/ref-manual/ref-variables.rst20
-rw-r--r--documentation/test-manual/test-manual-intro.rst4
-rw-r--r--documentation/toaster-manual/toaster-manual-intro.rst2
-rw-r--r--documentation/toaster-manual/toaster-manual-reference.rst8
22 files changed, 70 insertions, 70 deletions
diff --git a/documentation/adt-manual/adt-intro.rst b/documentation/adt-manual/adt-intro.rst
index d6228ad864..5372f4f54f 100644
--- a/documentation/adt-manual/adt-intro.rst
+++ b/documentation/adt-manual/adt-intro.rst
@@ -107,18 +107,18 @@ tools are common development tools for the Linux platform.
107 107
108- *PowerTOP:* Helps you determine what software is using the most 108- *PowerTOP:* Helps you determine what software is using the most
109 power. You can find out more about PowerTOP at 109 power. You can find out more about PowerTOP at
110 ` <https://01.org/powertop/>`__. 110 https://01.org/powertop/.
111 111
112- *OProfile:* A system-wide profiler for Linux systems that is capable 112- *OProfile:* A system-wide profiler for Linux systems that is capable
113 of profiling all running code at low overhead. You can find out more 113 of profiling all running code at low overhead. You can find out more
114 about OProfile at ` <http://oprofile.sourceforge.net/about/>`__. For 114 about OProfile at http://oprofile.sourceforge.net/about/. For
115 examples on how to setup and use this tool, see the 115 examples on how to setup and use this tool, see the
116 "`OProfile <&YOCTO_DOCS_PROF_URL;#profile-manual-oprofile>`__" 116 "`OProfile <&YOCTO_DOCS_PROF_URL;#profile-manual-oprofile>`__"
117 section in the Yocto Project Profiling and Tracing Manual. 117 section in the Yocto Project Profiling and Tracing Manual.
118 118
119- *Perf:* Performance counters for Linux used to keep track of certain 119- *Perf:* Performance counters for Linux used to keep track of certain
120 types of hardware and software events. For more information on these 120 types of hardware and software events. For more information on these
121 types of counters see ` <https://perf.wiki.kernel.org/>`__. For 121 types of counters see https://perf.wiki.kernel.org/. For
122 examples on how to setup and use this tool, see the 122 examples on how to setup and use this tool, see the
123 "`perf <&YOCTO_DOCS_PROF_URL;#profile-manual-perf>`__" section in the 123 "`perf <&YOCTO_DOCS_PROF_URL;#profile-manual-perf>`__" section in the
124 Yocto Project Profiling and Tracing Manual. 124 Yocto Project Profiling and Tracing Manual.
@@ -127,12 +127,12 @@ tools are common development tools for the Linux platform.
127 information gathering about a running Linux system. This information 127 information gathering about a running Linux system. This information
128 helps you diagnose performance or functional problems. SystemTap is 128 helps you diagnose performance or functional problems. SystemTap is
129 not available as a user-space tool through the Eclipse IDE Yocto 129 not available as a user-space tool through the Eclipse IDE Yocto
130 Plug-in. See ` <http://sourceware.org/systemtap>`__ for more 130 Plug-in. See http://sourceware.org/systemtap for more
131 information on SystemTap. For examples on how to setup and use this 131 information on SystemTap. For examples on how to setup and use this
132 tool, see the 132 tool, see the
133 "`SystemTap <&YOCTO_DOCS_PROF_URL;#profile-manual-systemtap>`__" 133 "`SystemTap <&YOCTO_DOCS_PROF_URL;#profile-manual-systemtap>`__"
134 section in the Yocto Project Profiling and Tracing Manual. 134 section in the Yocto Project Profiling and Tracing Manual.
135 135
136- *Lttng-ust:* A User-space Tracer designed to provide detailed 136- *Lttng-ust:* A User-space Tracer designed to provide detailed
137 information on user-space activity. See ` <http://lttng.org/ust>`__ 137 information on user-space activity. See http://lttng.org/ust
138 for more information on Lttng-ust. 138 for more information on Lttng-ust.
diff --git a/documentation/adt-manual/adt-package.rst b/documentation/adt-manual/adt-package.rst
index dfa62163b3..787d406e65 100644
--- a/documentation/adt-manual/adt-package.rst
+++ b/documentation/adt-manual/adt-package.rst
@@ -20,19 +20,19 @@ using three different Package Management Systems (PMS):
20- *OPKG:* A less well known PMS whose use originated in the 20- *OPKG:* A less well known PMS whose use originated in the
21 OpenEmbedded and OpenWrt embedded Linux projects. This PMS works with 21 OpenEmbedded and OpenWrt embedded Linux projects. This PMS works with
22 files packaged in an ``.ipk`` format. See 22 files packaged in an ``.ipk`` format. See
23 ` <http://en.wikipedia.org/wiki/Opkg>`__ for more information about 23 http://en.wikipedia.org/wiki/Opkg for more information about
24 OPKG. 24 OPKG.
25 25
26- *RPM:* A more widely known PMS intended for GNU/Linux distributions. 26- *RPM:* A more widely known PMS intended for GNU/Linux distributions.
27 This PMS works with files packaged in an ``.rpm`` format. The build 27 This PMS works with files packaged in an ``.rpm`` format. The build
28 system currently installs through this PMS by default. See 28 system currently installs through this PMS by default. See
29 ` <http://en.wikipedia.org/wiki/RPM_Package_Manager>`__ for more 29 http://en.wikipedia.org/wiki/RPM_Package_Manager for more
30 information about RPM. 30 information about RPM.
31 31
32- *Debian:* The PMS for Debian-based systems is built on many PMS 32- *Debian:* The PMS for Debian-based systems is built on many PMS
33 tools. The lower-level PMS tool ``dpkg`` forms the base of the Debian 33 tools. The lower-level PMS tool ``dpkg`` forms the base of the Debian
34 PMS. For information on dpkg see 34 PMS. For information on dpkg see
35 ` <http://en.wikipedia.org/wiki/Dpkg>`__. 35 http://en.wikipedia.org/wiki/Dpkg.
36 36
37Configuring the PMS 37Configuring the PMS
38=================== 38===================
diff --git a/documentation/adt-manual/adt-prepare.rst b/documentation/adt-manual/adt-prepare.rst
index 27133d21b4..e2141f8059 100644
--- a/documentation/adt-manual/adt-prepare.rst
+++ b/documentation/adt-manual/adt-prepare.rst
@@ -137,7 +137,7 @@ comments in the ``adt-installer.conf`` file:
137 set up your own IPKG repository pointed to by ``YOCTOADT_REPO``, you 137 set up your own IPKG repository pointed to by ``YOCTOADT_REPO``, you
138 need to be sure that the directory structure follows the same layout 138 need to be sure that the directory structure follows the same layout
139 as the reference directory set up at 139 as the reference directory set up at
140 ` <http://adtrepo.yoctoproject.org>`__. Also, your repository needs 140 http://adtrepo.yoctoproject.org. Also, your repository needs
141 to be accessible through HTTP. 141 to be accessible through HTTP.
142 142
143- ``YOCTOADT_TARGETS``: The machine target architectures for which you 143- ``YOCTOADT_TARGETS``: The machine target architectures for which you
@@ -572,7 +572,7 @@ follows:
572A good example of an external toolchain used with the Yocto Project is 572A good example of an external toolchain used with the Yocto Project is
573Mentor Graphics Sourcery G++ Toolchain. You can see information on how 573Mentor Graphics Sourcery G++ Toolchain. You can see information on how
574to use that particular layer in the ``README`` file at 574to use that particular layer in the ``README`` file at
575` <http://github.com/MentorEmbedded/meta-sourcery/>`__. You can find 575http://github.com/MentorEmbedded/meta-sourcery/. You can find
576further information by reading about the 576further information by reading about the
577:term:`TCMODE` variable in the Yocto 577:term:`TCMODE` variable in the Yocto
578Project Reference Manual's variable glossary. 578Project Reference Manual's variable glossary.
diff --git a/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst b/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst
index 8af70b4d46..850f3136c1 100644
--- a/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst
+++ b/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst
@@ -261,7 +261,7 @@ Follow these steps to add a hardware layer:
261 ``local.conf`` file specifies the machine for the build. For this 261 ``local.conf`` file specifies the machine for the build. For this
262 example, set the ``MACHINE`` variable to "cyclone5". These 262 example, set the ``MACHINE`` variable to "cyclone5". These
263 configurations are used: 263 configurations are used:
264 ` <https://github.com/kraj/meta-altera/blob/master/conf/machine/cyclone5.conf>`__. 264 https://github.com/kraj/meta-altera/blob/master/conf/machine/cyclone5.conf.
265 265
266 .. note:: 266 .. note::
267 267
diff --git a/documentation/bsp-guide/bsp.rst b/documentation/bsp-guide/bsp.rst
index 9a12c942bc..663d9478a4 100644
--- a/documentation/bsp-guide/bsp.rst
+++ b/documentation/bsp-guide/bsp.rst
@@ -108,7 +108,7 @@ Some layers function as a layer to hold other BSP layers. These layers
108are knows as "`container 108are knows as "`container
109layers <&YOCTO_DOCS_REF_URL;#term-container-layer>`__". An example of 109layers <&YOCTO_DOCS_REF_URL;#term-container-layer>`__". An example of
110this type of layer is OpenEmbedded's 110this type of layer is OpenEmbedded's
111```meta-openembedded`` <https://github.com/openembedded/meta-openembedded>`__ 111```meta-openembedded`https://github.com/openembedded/meta-openembedded
112layer. The ``meta-openembedded`` layer contains many ``meta-*`` layers. 112layer. The ``meta-openembedded`` layer contains many ``meta-*`` layers.
113In cases like this, you need to include the names of the actual layers 113In cases like this, you need to include the names of the actual layers
114you want to work with, such as: BBLAYERS ?= " \\ 114you want to work with, such as: BBLAYERS ?= " \\
@@ -164,7 +164,7 @@ section.
1644. *Optionally Clone the ``meta-intel`` BSP Layer:* If your hardware is 1644. *Optionally Clone the ``meta-intel`` BSP Layer:* If your hardware is
165 based on current Intel CPUs and devices, you can leverage this BSP 165 based on current Intel CPUs and devices, you can leverage this BSP
166 layer. For details on the ``meta-intel`` BSP layer, see the layer's 166 layer. For details on the ``meta-intel`` BSP layer, see the layer's
167 ```README`` <http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/README>`__ 167 ```README`http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/README
168 file. 168 file.
169 169
170 1. *Navigate to Your Source Directory:* Typically, you set up the 170 1. *Navigate to Your Source Directory:* Typically, you set up the
@@ -849,7 +849,7 @@ Yocto Project:
849 in ``poky/meta`` directory of the :term:`Source Directory` 849 in ``poky/meta`` directory of the :term:`Source Directory`
850 or in the 850 or in the
851 OpenEmbedded-Core Layer (``openembedded-core``) at 851 OpenEmbedded-Core Layer (``openembedded-core``) at
852 ` <http://git.openembedded.org/openembedded-core/tree/meta>`__. 852 http://git.openembedded.org/openembedded-core/tree/meta.
853 853
854 You should place recipes (``*.bb`` files) and recipe modifications 854 You should place recipes (``*.bb`` files) and recipe modifications
855 (``*.bbappend`` files) into ``recipes-*`` subdirectories by 855 (``*.bbappend`` files) into ``recipes-*`` subdirectories by
diff --git a/documentation/dev-manual/dev-manual-common-tasks.rst b/documentation/dev-manual/dev-manual-common-tasks.rst
index 0703f3ebc8..0807bd546f 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.rst
+++ b/documentation/dev-manual/dev-manual-common-tasks.rst
@@ -294,7 +294,7 @@ Logo for your layer and application. The process consists of two parts:
294 successful compatibility registration. 294 successful compatibility registration.
295 295
2962. Completion of an application acceptance form, which you can find at 2962. Completion of an application acceptance form, which you can find at
297 ` <https://www.yoctoproject.org/webform/yocto-project-compatible-registration>`__. 297 https://www.yoctoproject.org/webform/yocto-project-compatible-registration.
298 298
299To be granted permission to use the logo, you need to satisfy the 299To be granted permission to use the logo, you need to satisfy the
300following: 300following:
@@ -318,7 +318,7 @@ application, you can use the Yocto Project Compatibility Logo with your
318layer and the application that uses your layer. 318layer and the application that uses your layer.
319 319
320To access the form, use this link: 320To access the form, use this link:
321` <https://www.yoctoproject.org/webform/yocto-project-compatible-registration>`__. 321https://www.yoctoproject.org/webform/yocto-project-compatible-registration.
322Follow the instructions on the form to complete your application. 322Follow the instructions on the form to complete your application.
323 323
324The application consists of the following sections: 324The application consists of the following sections:
@@ -1713,7 +1713,7 @@ the software being built:
1713 install the built software into the directories. 1713 install the built software into the directories.
1714 1714
1715 You can find more information on ``install`` at 1715 You can find more information on ``install`` at
1716 ` <http://www.gnu.org/software/coreutils/manual/html_node/install-invocation.html>`__. 1716 http://www.gnu.org/software/coreutils/manual/html_node/install-invocation.html.
1717 1717
1718For the scenarios that do not use Autotools or CMake, you need to track 1718For the scenarios that do not use Autotools or CMake, you need to track
1719the installation and diagnose and fix any issues until everything 1719the installation and diagnose and fix any issues until everything
@@ -1796,7 +1796,7 @@ different ways:
1796- *systemd:* System Management Daemon (systemd) was designed to replace 1796- *systemd:* System Management Daemon (systemd) was designed to replace
1797 SysVinit and to provide enhanced management of services. For more 1797 SysVinit and to provide enhanced management of services. For more
1798 information on systemd, see the systemd homepage at 1798 information on systemd, see the systemd homepage at
1799 ` <http://freedesktop.org/wiki/Software/systemd/>`__. 1799 http://freedesktop.org/wiki/Software/systemd/.
1800 1800
1801 To enable a service using systemd, your recipe needs to inherit the 1801 To enable a service using systemd, your recipe needs to inherit the
1802 :ref:`systemd <ref-classes-systemd>` class. See 1802 :ref:`systemd <ref-classes-systemd>` class. See
@@ -1952,7 +1952,7 @@ recipe, but which one? You can configure your build to call out the
1952kernel recipe you want by using the 1952kernel recipe you want by using the
1953:term:`PREFERRED_PROVIDER` 1953:term:`PREFERRED_PROVIDER`
1954variable. As an example, consider the 1954variable. As an example, consider the
1955```x86-base.inc`` <https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/machine/include/x86-base.inc>`__ 1955```x86-base.inc`https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/machine/include/x86-base.inc
1956include file, which is a machine (i.e. 1956include file, which is a machine (i.e.
1957:term:`MACHINE`) configuration file. 1957:term:`MACHINE`) configuration file.
1958This include file is the reason all x86-based machines use the 1958This include file is the reason all x86-based machines use the
@@ -2806,7 +2806,7 @@ the layer tree.
2806 2806
2807You can easily set up to run the AUH utility on a regular basis by using 2807You can easily set up to run the AUH utility on a regular basis by using
2808a cron job. See the 2808a cron job. See the
2809```weeklyjob.sh`` <http://git.yoctoproject.org/cgit/cgit.cgi/auto-upgrade-helper/tree/weeklyjob.sh>`__ 2809```weeklyjob.sh`http://git.yoctoproject.org/cgit/cgit.cgi/auto-upgrade-helper/tree/weeklyjob.sh
2810file distributed with the utility for an example. 2810file distributed with the utility for an example.
2811 2811
2812.. _gs-using-devtool-upgrade: 2812.. _gs-using-devtool-upgrade:
@@ -4764,7 +4764,7 @@ follows:
4764A good example of an external toolchain used with the Yocto Project is 4764A good example of an external toolchain used with the Yocto Project is
4765Mentor Graphics Sourcery G++ Toolchain. You can see information on how 4765Mentor Graphics Sourcery G++ Toolchain. You can see information on how
4766to use that particular layer in the ``README`` file at 4766to use that particular layer in the ``README`` file at
4767` <http://github.com/MentorEmbedded/meta-sourcery/>`__. You can find 4767http://github.com/MentorEmbedded/meta-sourcery/. You can find
4768further information by reading about the 4768further information by reading about the
4769:term:`TCMODE` variable in the Yocto 4769:term:`TCMODE` variable in the Yocto
4770Project Reference Manual's variable glossary. 4770Project Reference Manual's variable glossary.
@@ -5583,7 +5583,7 @@ system to make your images more secure:
5583- Consider enabling a Mandatory Access Control (MAC) framework such as 5583- Consider enabling a Mandatory Access Control (MAC) framework such as
5584 SMACK or SELinux and tuning it appropriately for your device's usage. 5584 SMACK or SELinux and tuning it appropriately for your device's usage.
5585 You can find more information in the 5585 You can find more information in the
5586 ```meta-selinux`` <http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/>`__ 5586 ```meta-selinux`http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/
5587 layer. 5587 layer.
5588 5588
5589Tools for Hardening Your Image 5589Tools for Hardening Your Image
@@ -6690,7 +6690,7 @@ NPM packages:
6690 packages, the registry approach is slightly simpler. However, you 6690 packages, the registry approach is slightly simpler. However, you
6691 might consider the project approach because you do not have to 6691 might consider the project approach because you do not have to
6692 publish your module in the NPM registry 6692 publish your module in the NPM registry
6693 (```npm-registry`` <https://docs.npmjs.com/misc/registry>`__), which 6693 (```npm-registry`https://docs.npmjs.com/misc/registry), which
6694 is NPM's public registry. 6694 is NPM's public registry.
6695 6695
6696- Be familiar with 6696- Be familiar with
@@ -6698,7 +6698,7 @@ NPM packages:
6698 6698
6699- The NPM host tools need the native ``nodejs-npm`` package, which is 6699- The NPM host tools need the native ``nodejs-npm`` package, which is
6700 part of the OpenEmbedded environment. You need to get the package by 6700 part of the OpenEmbedded environment. You need to get the package by
6701 cloning the ` <https://github.com/openembedded/meta-openembedded>`__ 6701 cloning the https://github.com/openembedded/meta-openembedded
6702 repository out of GitHub. Be sure to add the path to your local copy 6702 repository out of GitHub. Be sure to add the path to your local copy
6703 to your ``bblayers.conf`` file. 6703 to your ``bblayers.conf`` file.
6704 6704
@@ -7547,7 +7547,7 @@ packages/qemux86_64-poky-linux/v86d/v86d: PKGSIZE changed from 110579 to
7547 7547
7548To see changes to the build history using a web interface, follow the 7548To see changes to the build history using a web interface, follow the
7549instruction in the ``README`` file here. 7549instruction in the ``README`` file here.
7550` <http://git.yoctoproject.org/cgit/cgit.cgi/buildhistory-web/>`__. 7550http://git.yoctoproject.org/cgit/cgit.cgi/buildhistory-web/.
7551 7551
7552Here is a sample screenshot of the interface: 7552Here is a sample screenshot of the interface:
7553 7553
@@ -8945,7 +8945,7 @@ style analysis of program crashes. GDB is available as a package within
8945the Yocto Project and is installed in SDK images by default. See the 8945the Yocto Project and is installed in SDK images by default. See the
8946":ref:`ref-manual/ref-images:Images`" chapter in the Yocto 8946":ref:`ref-manual/ref-images:Images`" chapter in the Yocto
8947Project Reference Manual for a description of these images. You can find 8947Project Reference Manual for a description of these images. You can find
8948information on GDB at ` <http://sourceware.org/gdb/>`__. 8948information on GDB at http://sourceware.org/gdb/.
8949 8949
8950.. note:: 8950.. note::
8951 8951
@@ -10086,7 +10086,7 @@ The server receives the information collected and saves it in a
10086database. 10086database.
10087 10087
10088A live instance of the error reporting server exists at 10088A live instance of the error reporting server exists at
10089` <http://errors.yoctoproject.org>`__. This server exists so that when 10089http://errors.yoctoproject.org. This server exists so that when
10090you want to get help with build failures, you can submit all of the 10090you want to get help with build failures, you can submit all of the
10091information on the failure easily and then point to the URL in your bug 10091information on the failure easily and then point to the URL in your bug
10092report or send an email to the mailing list. 10092report or send an email to the mailing list.
@@ -10119,7 +10119,7 @@ following command sends the errors to an upstream server: $
10119send-error-report 10119send-error-report
10120/home/brandusa/project/poky/build/tmp/log/error-report/error_report_201403141617.txt 10120/home/brandusa/project/poky/build/tmp/log/error-report/error_report_201403141617.txt
10121In the previous example, the errors are sent to a public database 10121In the previous example, the errors are sent to a public database
10122available at ` <http://errors.yoctoproject.org>`__, which is used by the 10122available at http://errors.yoctoproject.org, which is used by the
10123entire community. If you specify a particular server, you can send the 10123entire community. If you specify a particular server, you can send the
10124errors to a different database. Use the following command for more 10124errors to a different database. Use the following command for more
10125information on available options: $ send-error-report --help 10125information on available options: $ send-error-report --help
@@ -10145,7 +10145,7 @@ Setting Up Your Own Error Reporting Server
10145 10145
10146If you want to set up your own error reporting server, you can obtain 10146If you want to set up your own error reporting server, you can obtain
10147the code from the Git repository at 10147the code from the Git repository at
10148` <http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/>`__. 10148http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/.
10149Instructions on how to set it up are in the README document. 10149Instructions on how to set it up are in the README document.
10150 10150
10151.. _dev-using-wayland-and-weston: 10151.. _dev-using-wayland-and-weston:
diff --git a/documentation/dev-manual/dev-manual-start.rst b/documentation/dev-manual/dev-manual-start.rst
index 884d1286ef..b935f7b63e 100644
--- a/documentation/dev-manual/dev-manual-start.rst
+++ b/documentation/dev-manual/dev-manual-start.rst
@@ -445,14 +445,14 @@ as your Yocto Project build host:
445 445
4465. *Optionally Orient Yourself With Docker:* If you are unfamiliar with 4465. *Optionally Orient Yourself With Docker:* If you are unfamiliar with
447 Docker and the container concept, you can learn more here - 447 Docker and the container concept, you can learn more here -
448 ` <https://docs.docker.com/get-started/>`__. 448 https://docs.docker.com/get-started/.
449 449
4506. *Launch Docker or Docker Toolbox:* You should be able to launch 4506. *Launch Docker or Docker Toolbox:* You should be able to launch
451 Docker or the Docker Toolbox and have a terminal shell on your 451 Docker or the Docker Toolbox and have a terminal shell on your
452 development host. 452 development host.
453 453
4547. *Set Up the Containers to Use the Yocto Project:* Go to 4547. *Set Up the Containers to Use the Yocto Project:* Go to
455 ` <https://github.com/crops/docker-win-mac-docs/wiki>`__ and follow 455 https://github.com/crops/docker-win-mac-docs/wiki and follow
456 the directions for your particular build host (i.e. Linux, Mac, or 456 the directions for your particular build host (i.e. Linux, Mac, or
457 Windows). 457 Windows).
458 458
@@ -514,7 +514,7 @@ your Yocto Project build host:
514 514
5154. *Optionally Orient Yourself on WSL:* If you are unfamiliar with WSL, 5154. *Optionally Orient Yourself on WSL:* If you are unfamiliar with WSL,
516 you can learn more here - 516 you can learn more here -
517 ` <https://docs.microsoft.com/en-us/windows/wsl/wsl2-about>`__. 517 https://docs.microsoft.com/en-us/windows/wsl/wsl2-about.
518 518
5195. *Launch your WSL Distibution:* From the Windows start menu simply 5195. *Launch your WSL Distibution:* From the Windows start menu simply
520 launch your WSL distribution just like any other application. 520 launch your WSL distribution just like any other application.
diff --git a/documentation/kernel-dev/kernel-dev-common.rst b/documentation/kernel-dev/kernel-dev-common.rst
index aa9f77de86..ef3a9f710a 100644
--- a/documentation/kernel-dev/kernel-dev-common.rst
+++ b/documentation/kernel-dev/kernel-dev-common.rst
@@ -960,7 +960,7 @@ Using  ``menuconfig``
960The easiest way to define kernel configurations is to set them through 960The easiest way to define kernel configurations is to set them through
961the ``menuconfig`` tool. This tool provides an interactive method with 961the ``menuconfig`` tool. This tool provides an interactive method with
962which to set kernel configurations. For general information on 962which to set kernel configurations. For general information on
963``menuconfig``, see ` <http://en.wikipedia.org/wiki/Menuconfig>`__. 963``menuconfig``, see http://en.wikipedia.org/wiki/Menuconfig.
964 964
965To use the ``menuconfig`` tool in the Yocto Project development 965To use the ``menuconfig`` tool in the Yocto Project development
966environment, you must do the following: 966environment, you must do the following:
diff --git a/documentation/kernel-dev/kernel-dev-concepts-appx.rst b/documentation/kernel-dev/kernel-dev-concepts-appx.rst
index 165cbb9aef..a4611d1ae4 100644
--- a/documentation/kernel-dev/kernel-dev-concepts-appx.rst
+++ b/documentation/kernel-dev/kernel-dev-concepts-appx.rst
@@ -11,7 +11,7 @@ Yocto Project Kernel Development and Maintenance
11 11
12Kernels available through the Yocto Project (Yocto Linux kernels), like 12Kernels available through the Yocto Project (Yocto Linux kernels), like
13other kernels, are based off the Linux kernel releases from 13other kernels, are based off the Linux kernel releases from
14` <http://www.kernel.org>`__. At the beginning of a major Linux kernel 14http://www.kernel.org. At the beginning of a major Linux kernel
15development cycle, the Yocto Project team chooses a Linux kernel based 15development cycle, the Yocto Project team chooses a Linux kernel based
16on factors such as release timing, the anticipated release timing of 16on factors such as release timing, the anticipated release timing of
17final upstream ``kernel.org`` versions, and Yocto Project feature 17final upstream ``kernel.org`` versions, and Yocto Project feature
@@ -162,7 +162,7 @@ implemented by the Yocto Project team using the Source Code Manager
162 different work flows, front-ends and management techniques. 162 different work flows, front-ends and management techniques.
163 163
164 - You can find documentation on Git at 164 - You can find documentation on Git at
165 ` <http://git-scm.com/documentation>`__. You can also get an 165 http://git-scm.com/documentation. You can also get an
166 introduction to Git as it applies to the Yocto Project in the 166 introduction to Git as it applies to the Yocto Project in the
167 "`Git <&YOCTO_DOCS_OM_URL;#git>`__" section in the Yocto Project 167 "`Git <&YOCTO_DOCS_OM_URL;#git>`__" section in the Yocto Project
168 Overview and Concepts Manual. The latter reference provides an 168 Overview and Concepts Manual. The latter reference provides an
diff --git a/documentation/overview-manual/overview-manual-concepts.rst b/documentation/overview-manual/overview-manual-concepts.rst
index 978c2b0b6f..b49284911c 100644
--- a/documentation/overview-manual/overview-manual-concepts.rst
+++ b/documentation/overview-manual/overview-manual-concepts.rst
@@ -385,7 +385,7 @@ figure <#general-workflow-figure>`__:
385- *Metadata (``.bb`` + Patches):* Software layers containing 385- *Metadata (``.bb`` + Patches):* Software layers containing
386 user-supplied recipe files, patches, and append files. A good example 386 user-supplied recipe files, patches, and append files. A good example
387 of a software layer might be the 387 of a software layer might be the
388 ```meta-qt5`` <https://github.com/meta-qt5/meta-qt5>`__ layer from 388 ```meta-qt5`https://github.com/meta-qt5/meta-qt5 layer from
389 the `OpenEmbedded Layer 389 the `OpenEmbedded Layer
390 Index <http://layers.openembedded.org/layerindex/branch/master/layers/>`__. 390 Index <http://layers.openembedded.org/layerindex/branch/master/layers/>`__.
391 This layer is for version 5.0 of the popular 391 This layer is for version 5.0 of the popular
diff --git a/documentation/overview-manual/overview-manual-development-environment.rst b/documentation/overview-manual/overview-manual-development-environment.rst
index 65ad1d1206..f89e9b9dd4 100644
--- a/documentation/overview-manual/overview-manual-development-environment.rst
+++ b/documentation/overview-manual/overview-manual-development-environment.rst
@@ -381,12 +381,12 @@ commands.
381.. note:: 381.. note::
382 382
383 - For more information on Git, see 383 - For more information on Git, see
384 ` <http://git-scm.com/documentation>`__. 384 http://git-scm.com/documentation.
385 385
386 - If you need to download Git, it is recommended that you add Git to 386 - If you need to download Git, it is recommended that you add Git to
387 your system through your distribution's "software store" (e.g. for 387 your system through your distribution's "software store" (e.g. for
388 Ubuntu, use the Ubuntu Software feature). For the Git download 388 Ubuntu, use the Ubuntu Software feature). For the Git download
389 page, see ` <http://git-scm.com/download>`__. 389 page, see http://git-scm.com/download.
390 390
391 - For information beyond the introductory nature in this section, 391 - For information beyond the introductory nature in this section,
392 see the "`Locating Yocto Project Source 392 see the "`Locating Yocto Project Source
diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst
index dbd2aaf159..e25f0b278c 100644
--- a/documentation/ref-manual/faq.rst
+++ b/documentation/ref-manual/faq.rst
@@ -263,7 +263,7 @@ OpenEmbedded build system to use its internally built toolchain (i.e.
263particular, "external-*" refers to external toolchains. One example is 263particular, "external-*" refers to external toolchains. One example is
264the Sourcery G++ Toolchain. The support for this toolchain resides in 264the Sourcery G++ Toolchain. The support for this toolchain resides in
265the separate ``meta-sourcery`` layer at 265the separate ``meta-sourcery`` layer at
266` <http://github.com/MentorEmbedded/meta-sourcery/>`__. 266http://github.com/MentorEmbedded/meta-sourcery/.
267 267
268In addition to the toolchain configuration, you also need a 268In addition to the toolchain configuration, you also need a
269corresponding toolchain recipe file. This recipe file needs to package 269corresponding toolchain recipe file. This recipe file needs to package
diff --git a/documentation/ref-manual/migration.rst b/documentation/ref-manual/migration.rst
index 377932e2cf..a678580978 100644
--- a/documentation/ref-manual/migration.rst
+++ b/documentation/ref-manual/migration.rst
@@ -836,7 +836,7 @@ Following is a list of short entries describing other changes:
836 836
837- ``image.bbclass``: Move ``runtime_mapping_rename`` to avoid conflict 837- ``image.bbclass``: Move ``runtime_mapping_rename`` to avoid conflict
838 with ``multilib``. See 838 with ``multilib``. See
839 ```YOCTO #4993`` <https://bugzilla.yoctoproject.org/show_bug.cgi?id=4993>`__ 839 ```YOCTO #4993`https://bugzilla.yoctoproject.org/show_bug.cgi?id=4993
840 in Bugzilla for more information. 840 in Bugzilla for more information.
841 841
842- ``linux-dtb``: Use kernel build system to generate the ``dtb`` files. 842- ``linux-dtb``: Use kernel build system to generate the ``dtb`` files.
@@ -1658,9 +1658,9 @@ apply this
1658The standard ``linux-yocto`` kernel source tree already has a workaround 1658The standard ``linux-yocto`` kernel source tree already has a workaround
1659for the same issue. 1659for the same issue.
1660 1660
1661For further details, see ` <https://gcc.gnu.org/gcc-5/changes.html>`__ 1661For further details, see https://gcc.gnu.org/gcc-5/changes.html
1662and the porting guide at 1662and the porting guide at
1663` <https://gcc.gnu.org/gcc-5/porting_to.html>`__. 1663https://gcc.gnu.org/gcc-5/porting_to.html.
1664 1664
1665Alternatively, you can switch back to GCC 4.9 or 4.8 by setting 1665Alternatively, you can switch back to GCC 4.9 or 4.8 by setting
1666``GCCVERSION`` in your configuration, as follows: GCCVERSION = "4.9%" 1666``GCCVERSION`` in your configuration, as follows: GCCVERSION = "4.9%"
@@ -1991,13 +1991,13 @@ The use of ``${libdir}/${BPN}`` as ``libexecdir`` is different as
1991compared to all other mainstream distributions, which either uses 1991compared to all other mainstream distributions, which either uses
1992``${prefix}/libexec`` or ``${libdir}``. The use is also contrary to the 1992``${prefix}/libexec`` or ``${libdir}``. The use is also contrary to the
1993GNU Coding Standards (i.e. 1993GNU Coding Standards (i.e.
1994` <https://www.gnu.org/prep/standards/html_node/Directory-Variables.html>`__) 1994https://www.gnu.org/prep/standards/html_node/Directory-Variables.html)
1995that suggest ``${prefix}/libexec`` and also notes that any 1995that suggest ``${prefix}/libexec`` and also notes that any
1996package-specific nesting should be done by the package itself. Finally, 1996package-specific nesting should be done by the package itself. Finally,
1997having ``libexecdir`` change between recipes makes it very difficult for 1997having ``libexecdir`` change between recipes makes it very difficult for
1998different recipes to invoke binaries that have been installed into 1998different recipes to invoke binaries that have been installed into
1999``libexecdir``. The Filesystem Hierarchy Standard (i.e. 1999``libexecdir``. The Filesystem Hierarchy Standard (i.e.
2000` <http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html>`__) now 2000http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html) now
2001recognizes the use of ``${prefix}/libexec/``, giving distributions the 2001recognizes the use of ``${prefix}/libexec/``, giving distributions the
2002choice between ``${prefix}/lib`` or ``${prefix}/libexec`` without 2002choice between ``${prefix}/lib`` or ``${prefix}/libexec`` without
2003breaking FHS. 2003breaking FHS.
@@ -3874,7 +3874,7 @@ GCC 8.2 is Now Used by Default
3874 3874
3875The GNU Compiler Collection version 8.2 is now used by default for 3875The GNU Compiler Collection version 8.2 is now used by default for
3876compilation. For more information on what has changed in the GCC 8.x 3876compilation. For more information on what has changed in the GCC 8.x
3877release, see ` <https://gcc.gnu.org/gcc-8/changes.html>`__. 3877release, see https://gcc.gnu.org/gcc-8/changes.html.
3878 3878
3879If you still need to compile with version 7.x, GCC 7.3 is also provided. 3879If you still need to compile with version 7.x, GCC 7.3 is also provided.
3880You can select this version by setting the and can be selected by 3880You can select this version by setting the and can be selected by
@@ -4472,7 +4472,7 @@ The following miscellaneous changes occurred:
4472 from the top-level ``scripts`` directory. 4472 from the top-level ``scripts`` directory.
4473 4473
4474- Perl now builds for the target using 4474- Perl now builds for the target using
4475 ```perl-cross`` <http://arsv.github.io/perl-cross/>`__ for better 4475 ```perl-cross`http://arsv.github.io/perl-cross/ for better
4476 maintainability and improved build performance. This change should 4476 maintainability and improved build performance. This change should
4477 not present any problems unless you have heavily customized your Perl 4477 not present any problems unless you have heavily customized your Perl
4478 recipe. 4478 recipe.
@@ -4690,7 +4690,7 @@ The following BitBake changes have occurred.
4690 ```BB_HASHCHECK_FUNCTION`` <&YOCTO_DOCS_BB_URL;#var-bb-BB_HASHCHECK_FUNCTION>`__ 4690 ```BB_HASHCHECK_FUNCTION`` <&YOCTO_DOCS_BB_URL;#var-bb-BB_HASHCHECK_FUNCTION>`__
4691 have changed. If you are using your own custom hash check function, 4691 have changed. If you are using your own custom hash check function,
4692 see 4692 see
4693 ` <http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725>`__ 4693 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725
4694 for details. 4694 for details.
4695 4695
4696- Task specifications in ``BB_TASKDEPDATA`` and class implementations 4696- Task specifications in ``BB_TASKDEPDATA`` and class implementations
diff --git a/documentation/ref-manual/ref-classes.rst b/documentation/ref-manual/ref-classes.rst
index ae5f0e40d1..ace69e15a7 100644
--- a/documentation/ref-manual/ref-classes.rst
+++ b/documentation/ref-manual/ref-classes.rst
@@ -283,7 +283,7 @@ The ``ccache`` class enables the C/C++ Compiler Cache for the build.
283This class is used to give a minor performance boost during the build. 283This class is used to give a minor performance boost during the build.
284However, using the class can lead to unexpected side-effects. Thus, it 284However, using the class can lead to unexpected side-effects. Thus, it
285is recommended that you do not use this class. See 285is recommended that you do not use this class. See
286` <http://ccache.samba.org/>`__ for information on the C/C++ Compiler 286http://ccache.samba.org/ for information on the C/C++ Compiler
287Cache. 287Cache.
288 288
289.. _ref-classes-chrpath: 289.. _ref-classes-chrpath:
diff --git a/documentation/ref-manual/ref-devtool-reference.rst b/documentation/ref-manual/ref-devtool-reference.rst
index 8965b38ffa..418c9623f6 100644
--- a/documentation/ref-manual/ref-devtool-reference.rst
+++ b/documentation/ref-manual/ref-devtool-reference.rst
@@ -287,7 +287,7 @@ particular recipe.
287.. note:: 287.. note::
288 288
289 - For the ``oe-core`` layer, recipe maintainers come from the 289 - For the ``oe-core`` layer, recipe maintainers come from the
290 ```maintainers.inc`` <http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc>`__ 290 ```maintainers.inc`http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
291 file. 291 file.
292 292
293 - If the recipe is using the `Git 293 - If the recipe is using the `Git
diff --git a/documentation/ref-manual/ref-kickstart.rst b/documentation/ref-manual/ref-kickstart.rst
index 5f8c834f33..271e6e8509 100644
--- a/documentation/ref-manual/ref-kickstart.rst
+++ b/documentation/ref-manual/ref-kickstart.rst
@@ -155,7 +155,7 @@ the ``part`` and ``partition`` commands:
155- *``--part-type``:* This option is a Wic-specific option that 155- *``--part-type``:* This option is a Wic-specific option that
156 specifies the partition type globally unique identifier (GUID) for 156 specifies the partition type globally unique identifier (GUID) for
157 GPT partitions. You can find the list of partition type GUIDs at 157 GPT partitions. You can find the list of partition type GUIDs at
158 ` <http://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs>`__. 158 http://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs.
159 159
160- *``--use-uuid``:* This option is a Wic-specific option that causes 160- *``--use-uuid``:* This option is a Wic-specific option that causes
161 Wic to generate a random GUID for the partition. The generated 161 Wic to generate a random GUID for the partition. The generated
diff --git a/documentation/ref-manual/ref-qa-checks.rst b/documentation/ref-manual/ref-qa-checks.rst
index d60c0616f0..a56de690b1 100644
--- a/documentation/ref-manual/ref-qa-checks.rst
+++ b/documentation/ref-manual/ref-qa-checks.rst
@@ -212,7 +212,7 @@ Errors and Warnings
212 you could add the following to your recipe: CFLAGS_append = " -fPIC " 212 you could add the following to your recipe: CFLAGS_append = " -fPIC "
213 213
214 For more information on text relocations at runtime, see 214 For more information on text relocations at runtime, see
215 ` <http://www.akkadia.org/drepper/textrelocs.html>`__. 215 http://www.akkadia.org/drepper/textrelocs.html.
216 216
217   217  
218 218
diff --git a/documentation/ref-manual/ref-release-process.rst b/documentation/ref-manual/ref-release-process.rst
index 832f011918..7b33c0ae6b 100644
--- a/documentation/ref-manual/ref-release-process.rst
+++ b/documentation/ref-manual/ref-release-process.rst
@@ -54,7 +54,7 @@ codename are likely to be compatible and thus work together.
54Releases are given a nominal release version as well but the codename is 54Releases are given a nominal release version as well but the codename is
55used in repositories for this reason. You can find information on Yocto 55used in repositories for this reason. You can find information on Yocto
56Project releases and codenames at 56Project releases and codenames at
57` <https://wiki.yoctoproject.org/wiki/Releases>`__. 57https://wiki.yoctoproject.org/wiki/Releases.
58 58
59Stable Release Process 59Stable Release Process
60====================== 60======================
@@ -84,7 +84,7 @@ Community LTS trees and branches exist where community members share
84patches for older releases. However, these types of patches do not go 84patches for older releases. However, these types of patches do not go
85through the same release process as do point releases. You can find more 85through the same release process as do point releases. You can find more
86information about stable branch maintenance at 86information about stable branch maintenance at
87` <https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance>`__. 87https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance.
88 88
89Testing and Quality Assurance 89Testing and Quality Assurance
90============================= 90=============================
diff --git a/documentation/ref-manual/ref-variables.rst b/documentation/ref-manual/ref-variables.rst
index 53e99a395a..205a060103 100644
--- a/documentation/ref-manual/ref-variables.rst
+++ b/documentation/ref-manual/ref-variables.rst
@@ -546,7 +546,7 @@ system and gives an overview of their function and contents.
546 software. 546 software.
547 547
548 When specifying recipe files, you can pattern match using Python's 548 When specifying recipe files, you can pattern match using Python's
549 ```glob`` <https://docs.python.org/3/library/glob.html>`__ syntax. 549 ```glob`https://docs.python.org/3/library/glob.html syntax.
550 For details on the syntax, see the documentation by following the 550 For details on the syntax, see the documentation by following the
551 previous link. 551 previous link.
552 552
@@ -604,7 +604,7 @@ system and gives an overview of their function and contents.
604 compiler. Consequently, the syntax follows Python's Regular 604 compiler. Consequently, the syntax follows Python's Regular
605 Expression (re) syntax. The expressions are compared against the full 605 Expression (re) syntax. The expressions are compared against the full
606 paths to the files. For complete syntax information, see Python's 606 paths to the files. For complete syntax information, see Python's
607 documentation at ` <http://docs.python.org/3/library/re.html#re>`__. 607 documentation at http://docs.python.org/3/library/re.html#re.
608 608
609 The following example uses a complete regular expression to tell 609 The following example uses a complete regular expression to tell
610 BitBake to ignore all recipe and recipe append files in the 610 BitBake to ignore all recipe and recipe append files in the
@@ -2173,7 +2173,7 @@ system and gives an overview of their function and contents.
2173 2173
2174 - When specifying files or paths, you can pattern match using 2174 - When specifying files or paths, you can pattern match using
2175 Python's 2175 Python's
2176 ```glob`` <https://docs.python.org/2/library/glob.html>`__ 2176 ```glob`https://docs.python.org/2/library/glob.html
2177 syntax. For details on the syntax, see the documentation by 2177 syntax. For details on the syntax, see the documentation by
2178 following the previous link. 2178 following the previous link.
2179 2179
@@ -2435,7 +2435,7 @@ system and gives an overview of their function and contents.
2435 2435
2436 Here is an example from the ``dbus`` recipe: GROUPADD_PARAM_${PN} = 2436 Here is an example from the ``dbus`` recipe: GROUPADD_PARAM_${PN} =
2437 "-r netdev" For information on the standard Linux shell command 2437 "-r netdev" For information on the standard Linux shell command
2438 ``groupadd``, see ` <http://linux.die.net/man/8/groupadd>`__. 2438 ``groupadd``, see http://linux.die.net/man/8/groupadd.
2439 2439
2440 GROUPMEMS_PARAM 2440 GROUPMEMS_PARAM
2441 When inheriting the :ref:`useradd <ref-classes-useradd>` class, 2441 When inheriting the :ref:`useradd <ref-classes-useradd>` class,
@@ -2444,7 +2444,7 @@ system and gives an overview of their function and contents.
2444 of a group when the package is installed. 2444 of a group when the package is installed.
2445 2445
2446 For information on the standard Linux shell command ``groupmems``, 2446 For information on the standard Linux shell command ``groupmems``,
2447 see ` <http://linux.die.net/man/8/groupmems>`__. 2447 see http://linux.die.net/man/8/groupmems.
2448 2448
2449 GRUB_GFXSERIAL 2449 GRUB_GFXSERIAL
2450 Configures the GNU GRand Unified Bootloader (GRUB) to have graphics 2450 Configures the GNU GRand Unified Bootloader (GRUB) to have graphics
@@ -3313,7 +3313,7 @@ system and gives an overview of their function and contents.
3313 The value in ``INITSCRIPT_PARAMS`` is passed through to the 3313 The value in ``INITSCRIPT_PARAMS`` is passed through to the
3314 ``update-rc.d`` command. For more information on valid parameters, 3314 ``update-rc.d`` command. For more information on valid parameters,
3315 please see the ``update-rc.d`` manual page at 3315 please see the ``update-rc.d`` manual page at
3316 ` <http://www.tin.org/bin/man.cgi?section=8&topic=update-rc.d>`__. 3316 http://www.tin.org/bin/man.cgi?section=8&topic=update-rc.d.
3317 3317
3318 INSANE_SKIP 3318 INSANE_SKIP
3319 Specifies the QA checks to skip for a specific package within a 3319 Specifies the QA checks to skip for a specific package within a
@@ -4193,7 +4193,7 @@ system and gives an overview of their function and contents.
4193 variable for more information. 4193 variable for more information.
4194 4194
4195 module_conf 4195 module_conf
4196 Specifies ```modprobe.d`` <http://linux.die.net/man/5/modprobe.d>`__ 4196 Specifies ```modprobe.d`http://linux.die.net/man/5/modprobe.d
4197 syntax lines for inclusion in the ``/etc/modprobe.d/modname.conf`` 4197 syntax lines for inclusion in the ``/etc/modprobe.d/modname.conf``
4198 file. 4198 file.
4199 4199
@@ -7069,7 +7069,7 @@ system and gives an overview of their function and contents.
7069 toolchain. One example is the Sourcery G++ Toolchain. The support for 7069 toolchain. One example is the Sourcery G++ Toolchain. The support for
7070 this toolchain resides in the separate Mentor Graphics 7070 this toolchain resides in the separate Mentor Graphics
7071 ``meta-sourcery`` layer at 7071 ``meta-sourcery`` layer at
7072 ` <http://github.com/MentorEmbedded/meta-sourcery/>`__. 7072 http://github.com/MentorEmbedded/meta-sourcery/.
7073 7073
7074 The layer's ``README`` file contains information on how to use the 7074 The layer's ``README`` file contains information on how to use the
7075 Sourcery G++ Toolchain as an external toolchain. In summary, you must 7075 Sourcery G++ Toolchain as an external toolchain. In summary, you must
@@ -7527,7 +7527,7 @@ system and gives an overview of their function and contents.
7527 "sdcard" specifies the ``IMAGE_FSTYPES`` to use for the U-boot image. 7527 "sdcard" specifies the ``IMAGE_FSTYPES`` to use for the U-boot image.
7528 7528
7529 For more information on how the ``UBOOT_CONFIG`` is handled, see the 7529 For more information on how the ``UBOOT_CONFIG`` is handled, see the
7530 ```uboot-config`` <http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/uboot-config.bbclass>`__ 7530 ```uboot-config`http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/uboot-config.bbclass
7531 class. 7531 class.
7532 7532
7533 UBOOT_ENTRYPOINT 7533 UBOOT_ENTRYPOINT
@@ -7787,7 +7787,7 @@ system and gives an overview of their function and contents.
7787 "--system --home ${localstatedir}/lib/dbus \\ --no-create-home 7787 "--system --home ${localstatedir}/lib/dbus \\ --no-create-home
7788 --shell /bin/false \\ --user-group messagebus" For information on the 7788 --shell /bin/false \\ --user-group messagebus" For information on the
7789 standard Linux shell command ``useradd``, see 7789 standard Linux shell command ``useradd``, see
7790 ` <http://linux.die.net/man/8/useradd>`__. 7790 http://linux.die.net/man/8/useradd.
7791 7791
7792 USERADD_UID_TABLES 7792 USERADD_UID_TABLES
7793 Specifies a password file to use for obtaining static user 7793 Specifies a password file to use for obtaining static user
diff --git a/documentation/test-manual/test-manual-intro.rst b/documentation/test-manual/test-manual-intro.rst
index dc8de45fa8..2f11e2beb3 100644
--- a/documentation/test-manual/test-manual-intro.rst
+++ b/documentation/test-manual/test-manual-intro.rst
@@ -27,7 +27,7 @@ loaded with information from the `README <>`__ files and notes from key
27engineers: 27engineers:
28 28
29- *``yocto-autobuilder2``:* This 29- *``yocto-autobuilder2``:* This
30 ```README.md`` <http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder2/tree/README.md>`__ 30 ```README.md`http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder2/tree/README.md
31 is the main README which detials how to set up the Yocto Project 31 is the main README which detials how to set up the Yocto Project
32 Autobuilder. The ``yocto-autobuilder2`` repository represents the 32 Autobuilder. The ``yocto-autobuilder2`` repository represents the
33 Yocto Project's console UI plugin to Buildbot and the configuration 33 Yocto Project's console UI plugin to Buildbot and the configuration
@@ -35,7 +35,7 @@ engineers:
35 requires. 35 requires.
36 36
37- *``yocto-autobuilder-helper``:* This 37- *``yocto-autobuilder-helper``:* This
38 ```README`` <http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder-helper/tree/README>`__ 38 ```README`http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder-helper/tree/README
39 and repository contains Yocto Project Autobuilder Helper scripts and 39 and repository contains Yocto Project Autobuilder Helper scripts and
40 configuration. The ``yocto-autobuilder-helper`` repository contains 40 configuration. The ``yocto-autobuilder-helper`` repository contains
41 the "glue" logic that defines which tests to run and how to run them. 41 the "glue" logic that defines which tests to run and how to run them.
diff --git a/documentation/toaster-manual/toaster-manual-intro.rst b/documentation/toaster-manual/toaster-manual-intro.rst
index c9d2617394..cc972f7c73 100644
--- a/documentation/toaster-manual/toaster-manual-intro.rst
+++ b/documentation/toaster-manual/toaster-manual-intro.rst
@@ -29,7 +29,7 @@ extensive information about the build process.
29 - Browse layers listed in the various `layer 29 - Browse layers listed in the various `layer
30 sources <#layer-source>`__ that are available in your project 30 sources <#layer-source>`__ that are available in your project
31 (e.g. the OpenEmbedded Layer Index at 31 (e.g. the OpenEmbedded Layer Index at
32 ` <http://layers.openembedded.org/layerindex/>`__). 32 http://layers.openembedded.org/layerindex/).
33 33
34 - Browse images, recipes, and machines provided by those layers. 34 - Browse images, recipes, and machines provided by those layers.
35 35
diff --git a/documentation/toaster-manual/toaster-manual-reference.rst b/documentation/toaster-manual/toaster-manual-reference.rst
index 0494f55d9e..a628c78cc2 100644
--- a/documentation/toaster-manual/toaster-manual-reference.rst
+++ b/documentation/toaster-manual/toaster-manual-reference.rst
@@ -24,9 +24,9 @@ type of layer source called a "layer index."
24A layer index is a web application that contains information about a set 24A layer index is a web application that contains information about a set
25of custom layers. A good example of an existing layer index is the 25of custom layers. A good example of an existing layer index is the
26OpenEmbedded Layer Index. A public instance of this layer index exists 26OpenEmbedded Layer Index. A public instance of this layer index exists
27at ` <http://layers.openembedded.org>`__. You can find the code for this 27at http://layers.openembedded.org. You can find the code for this
28layer index's web application at 28layer index's web application at
29` <http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/>`__. 29http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/.
30 30
31When you tie a layer source into Toaster, it can query the layer source 31When you tie a layer source into Toaster, it can query the layer source
32through a 32through a
@@ -87,9 +87,9 @@ describes two methods by which you can configure and use your layer
87index. 87index.
88 88
89In the previous section, the code for the OpenEmbedded Metadata Index 89In the previous section, the code for the OpenEmbedded Metadata Index
90(i.e. ` <http://layers.openembedded.org>`__) was referenced. You can use 90(i.e. http://layers.openembedded.org) was referenced. You can use
91this code, which is at 91this code, which is at
92` <http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/>`__, as a 92http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/, as a
93base to create your own layer index. 93base to create your own layer index.
94 94
95Use the Administration Interface 95Use the Administration Interface