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

dev-manual: Review edits to how to find checksum values. 

Edits from Paul to better word this section.

(From yocto-docs rev: 51425ab506050ee5ba30d5c3c10639d5a1b8cc8e)

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 2014-08-05 08:38:02 +03:00 committed by Richard Purdie
parent e2e08444bc
commit a20e75f45b
1 changed files with 17 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -1797,10 +1797,10 @@
</para> </para>
<para> <para>
Finding proper values for <filename>md5</filename> and Proper values for <filename>md5</filename> and
<filename>sha256</filename> checksums can involve some work. <filename>sha256</filename> checksums might be available
Initially, you should locate any available signatures from with other signatures on the download page for the upstream
the upstream source (i.e. <filename>md5</filename>, source (e.g. <filename>md5</filename>,
<filename>sha1</filename>, <filename>sha256</filename>, <filename>sha1</filename>, <filename>sha256</filename>,
<filename>GPG</filename>, and so forth). <filename>GPG</filename>, and so forth).
Because the OpenEmbedded build system only deals with Because the OpenEmbedded build system only deals with
@ -1809,18 +1809,19 @@
</para> </para>
<para> <para>
After you have verified as many signatures as you can, If no <filename>SRC_URI</filename> checksums are specified
you can use a "build-fail" method that retrieves the exact when you attempt to build the recipe, the build will produce
<filename>sha256sum</filename> and <filename>md5sum</filename> an error for each missing checksum.
checksums you need. As part of the error message, the build system provides
To use the "build-fail" method, comment the the checksum string corresponding to the fetched file.
<filename>SRC_URI</filename> statements out that provide the Once you have the correct checksums, you can copy and paste
checksums and then attempt to build the software. them into your recipe and then run the build again to continue.
The build will produce an error for each missing checksum <note>
and as part of the error message provide the correct checksum As mentioned, if the upstream source provides signatures
string. for verifying the downloaded source code, you should
Once you have the correct checksums, simply copy them into your verify those manually before setting the checksum values
recipe for a subsequent build. in the recipe and continuing with the build.
</note>
</para> </para>
<para> <para>