diff options
| author |   Scott Rifenbark <scott.m.rifenbark@intel.com> | 2015-01-19 07:32:34 -0800 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-02-17 15:16:50 +0000 |
| commit | f8245d98eae2f3d3968a00d99b1f04f1cddda04a (patch) | |
| tree | 7d4001a9a255dea1cc3c53fdd245c664e391a794 /documentation/dev-manual/dev-manual-common-tasks.xml | |
| parent | 4492b37a06018d13a0863eb5a8a651d4e48aa669 (diff) | |
| download | openembedded-core-contrib-f8245d98eae2f3d3968a00d99b1f04f1cddda04a.tar.gz | |
dev-manual: Updated section on how checksums are dealt with
In the "Fetching Code" section, some loose description of how the
build system reacts to the two checksums in a recipe existed.
Robert asked some questions about how the behavior would be if
just a single, correct checksum existed and if the two existed but
only one proved correct. Turns out, if you supply a single one then
the build will not throw an error or warning. If you supply two
but one is incorrect, then the build will throw an error or
warning. I updated the text to be technically correct without
going into huge details.
(From yocto-docs rev: f49a744821d9326314803d5003158bd402e74e0d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml')
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index e3c312ce0d..3b675359b5 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1836,8 +1836,9 @@ <para> If no <filename>SRC_URI</filename> checksums are specified - when you attempt to build the recipe, the build will produce - an error for each missing checksum. + when you attempt to build the recipe, or you provide an + incorrect checksum, the build will produce an error for each + missing or incorrect checksum. As part of the error message, the build system provides the checksum string corresponding to the fetched file. Once you have the correct checksums, you can copy and paste |