summaryrefslogtreecommitdiffstats
path: root/documentation/sdk-manual/appendix-obtain.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/sdk-manual/appendix-obtain.rst')
-rw-r--r--documentation/sdk-manual/appendix-obtain.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/sdk-manual/appendix-obtain.rst b/documentation/sdk-manual/appendix-obtain.rst
index ad531cbf24..d06d6ec6b5 100644
--- a/documentation/sdk-manual/appendix-obtain.rst
+++ b/documentation/sdk-manual/appendix-obtain.rst
@@ -66,7 +66,7 @@ Follow these steps to locate and hand-install the toolchain:
66 poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-&DISTRO;.sh 66 poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-&DISTRO;.sh
67 67
68#. *Run the Installer:* Be sure you have execution privileges and run 68#. *Run the Installer:* Be sure you have execution privileges and run
69 the installer. Following is an example from the ``Downloads`` 69 the installer. Here is an example from the ``Downloads``
70 directory:: 70 directory::
71 71
72 $ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-&DISTRO;.sh 72 $ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-&DISTRO;.sh
@@ -165,12 +165,12 @@ build the SDK installer. Follow these steps:
165 variable inside your ``local.conf`` file before building the 165 variable inside your ``local.conf`` file before building the
166 SDK installer. Doing so ensures that the eventual SDK 166 SDK installer. Doing so ensures that the eventual SDK
167 installation process installs the appropriate library packages 167 installation process installs the appropriate library packages
168 as part of the SDK. Following is an example using ``libc`` 168 as part of the SDK. Here is an example using ``libc``
169 static development libraries: TOOLCHAIN_TARGET_TASK:append = " 169 static development libraries: TOOLCHAIN_TARGET_TASK:append = "
170 libc-staticdev" 170 libc-staticdev"
171 171
172#. *Run the Installer:* You can now run the SDK installer from 172#. *Run the Installer:* You can now run the SDK installer from
173 ``tmp/deploy/sdk`` in the :term:`Build Directory`. Following is an example:: 173 ``tmp/deploy/sdk`` in the :term:`Build Directory`. Here is an example::
174 174
175 $ cd poky/build/tmp/deploy/sdk 175 $ cd poky/build/tmp/deploy/sdk
176 $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh 176 $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
@@ -235,7 +235,7 @@ Follow these steps to extract the root filesystem:
235 This script is located in the top-level directory in which you 235 This script is located in the top-level directory in which you
236 installed the toolchain (e.g. ``poky_sdk``). 236 installed the toolchain (e.g. ``poky_sdk``).
237 237
238 Following is an example based on the toolchain installed in the 238 Here is an example based on the toolchain installed in the
239 ":ref:`sdk-manual/appendix-obtain:locating pre-built sdk installers`" section:: 239 ":ref:`sdk-manual/appendix-obtain:locating pre-built sdk installers`" section::
240 240
241 $ source poky_sdk/environment-setup-core2-64-poky-linux 241 $ source poky_sdk/environment-setup-core2-64-poky-linux
@@ -243,7 +243,7 @@ Follow these steps to extract the root filesystem:
243#. *Extract the Root Filesystem:* Use the ``runqemu-extract-sdk`` 243#. *Extract the Root Filesystem:* Use the ``runqemu-extract-sdk``
244 command and provide the root filesystem image. 244 command and provide the root filesystem image.
245 245
246 Following is an example command that extracts the root filesystem 246 Here is an example command that extracts the root filesystem
247 from a previously built root filesystem image that was downloaded 247 from a previously built root filesystem image that was downloaded
248 from the :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`. 248 from the :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`.
249 This command extracts the root filesystem into the ``core2-64-sato`` 249 This command extracts the root filesystem into the ``core2-64-sato``