sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

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>
This commit is contained in:
Scott Rifenbark 2012-09-27 12:12:15 -06:00 committed by Richard Purdie
parent b99414e1d4
commit 7c39c87d52
2 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
documentation/adt-manual/adt-prepare.xml
View File

@ -265,8 +265,10 @@
be in <filename>tmp/deploy/sdk</filename> in the build directory.
</para></note>
</para></listitem>
<listitem><para>Once you have the installer, run it to install the toolchain.
The following command shows how to run the installer given a toolchain tarball
<listitem><para>Once you have the installer, run it to install the toolchain.
You must change the permissions on the toolchain installer
script so that it is executable.</para>
<para>The following command shows how to run the installer given a toolchain tarball
for a 64-bit development host system and a 32-bit target architecture.
The example assumes the toolchain installer is located in <filename>~/Downloads/</filename>.
<literallayout class='monospaced'>

5
documentation/yocto-project-qs/yocto-project-qs.xml
View File

@ -572,6 +572,11 @@
<para>
The following command shows how to run the installer given a toolchain tarball
for a 64-bit development host system and a 32-bit target architecture.
You must change the permissions on the toolchain
installer script so that it is executable.
</para>
<para>
The example assumes the toolchain installer is located in <filename>~/Downloads/</filename>.
<note>
If you do not have write permissions for the directory into which you are installing