summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual/adt-prepare.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-09-27 12:12:15 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-09-28 17:54:28 +0100
commit7c39c87d52c20e47cf90275a16e4517a296c8388 (patch)
treec67dd12a6e049da11684ca1cf7842abdadc54cb1 /documentation/adt-manual/adt-prepare.xml
parentb99414e1d45dde4c030a17b15ec44da817261086 (diff)
downloadpoky-7c39c87d52c20e47cf90275a16e4517a296c8388.tar.gz
documentation: adt-manual, yocto-project-qs - Added tarball installer info
Turns out the .sh file that installs the tarball comes down without executable permissions. I added a sentence in each manual instructing the user to set the permissions to the script before attempting to run it. (From yocto-docs rev: c1699971b3e03893aa1af5033e19d8f5c0b21ff4) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/adt-manual/adt-prepare.xml')
-rw-r--r--documentation/adt-manual/adt-prepare.xml6
1 files changed, 4 insertions, 2 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 5957915419..d660480b73 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -265,8 +265,10 @@
265 be in <filename>tmp/deploy/sdk</filename> in the build directory. 265 be in <filename>tmp/deploy/sdk</filename> in the build directory.
266 </para></note> 266 </para></note>
267 </para></listitem> 267 </para></listitem>
268 <listitem><para>Once you have the installer, run it to install the toolchain. 268 <listitem><para>Once you have the installer, run it to install the toolchain.
269 The following command shows how to run the installer given a toolchain tarball 269 You must change the permissions on the toolchain installer
270 script so that it is executable.</para>
271 <para>The following command shows how to run the installer given a toolchain tarball
270 for a 64-bit development host system and a 32-bit target architecture. 272 for a 64-bit development host system and a 32-bit target architecture.
271 The example assumes the toolchain installer is located in <filename>~/Downloads/</filename>. 273 The example assumes the toolchain installer is located in <filename>~/Downloads/</filename>.
272 <literallayout class='monospaced'> 274 <literallayout class='monospaced'>