summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-08-05 08:38:02 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-08-12 13:50:30 +0100
commita20e75f45bcf156e472b7135b04e1f4f8fd70ce4 (patch)
tree9a9ce202f070cbf1f7fa8cac2784a47289c18924
parente2e08444bca27cc8337c9acc07f4f99b0885bb9c (diff)
downloadpoky-a20e75f45bcf156e472b7135b04e1f4f8fd70ce4.tar.gz
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>
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml33
1 files changed, 17 insertions, 16 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index e5c1649f57..0218dc59fd 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1797,10 +1797,10 @@
1797 </para> 1797 </para>
1798 1798
1799 <para> 1799 <para>
1800 Finding proper values for <filename>md5</filename> and 1800 Proper values for <filename>md5</filename> and
1801 <filename>sha256</filename> checksums can involve some work. 1801 <filename>sha256</filename> checksums might be available
1802 Initially, you should locate any available signatures from 1802 with other signatures on the download page for the upstream
1803 the upstream source (i.e. <filename>md5</filename>, 1803 source (e.g. <filename>md5</filename>,
1804 <filename>sha1</filename>, <filename>sha256</filename>, 1804 <filename>sha1</filename>, <filename>sha256</filename>,
1805 <filename>GPG</filename>, and so forth). 1805 <filename>GPG</filename>, and so forth).
1806 Because the OpenEmbedded build system only deals with 1806 Because the OpenEmbedded build system only deals with
@@ -1809,18 +1809,19 @@
1809 </para> 1809 </para>
1810 1810
1811 <para> 1811 <para>
1812 After you have verified as many signatures as you can, 1812 If no <filename>SRC_URI</filename> checksums are specified
1813 you can use a "build-fail" method that retrieves the exact 1813 when you attempt to build the recipe, the build will produce
1814 <filename>sha256sum</filename> and <filename>md5sum</filename> 1814 an error for each missing checksum.
1815 checksums you need. 1815 As part of the error message, the build system provides
1816 To use the "build-fail" method, comment the 1816 the checksum string corresponding to the fetched file.
1817 <filename>SRC_URI</filename> statements out that provide the 1817 Once you have the correct checksums, you can copy and paste
1818 checksums and then attempt to build the software. 1818 them into your recipe and then run the build again to continue.
1819 The build will produce an error for each missing checksum 1819 <note>
1820 and as part of the error message provide the correct checksum 1820 As mentioned, if the upstream source provides signatures
1821 string. 1821 for verifying the downloaded source code, you should
1822 Once you have the correct checksums, simply copy them into your 1822 verify those manually before setting the checksum values
1823 recipe for a subsequent build. 1823 in the recipe and continuing with the build.
1824 </note>
1824 </para> 1825 </para>
1825 1826
1826 <para> 1827 <para>