diff options
| -rw-r--r-- | bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst index 4dadf0bc7b..6a3488ed23 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst | |||
| @@ -2228,12 +2228,12 @@ OpenEmbedded metadata-based example. | |||
| 2228 | These checksums are stored in :term:`STAMP`. You can | 2228 | These checksums are stored in :term:`STAMP`. You can |
| 2229 | examine the checksums using the following BitBake command:: | 2229 | examine the checksums using the following BitBake command:: |
| 2230 | 2230 | ||
| 2231 | $ bitbake-dumpsigs | 2231 | $ bitbake-dumpsig |
| 2232 | 2232 | ||
| 2233 | This command returns the signature data in a readable | 2233 | This command returns the signature data in a readable |
| 2234 | format that allows you to examine the inputs used when the OpenEmbedded | 2234 | format that allows you to examine the inputs used when the OpenEmbedded |
| 2235 | build system generates signatures. For example, using | 2235 | build system generates signatures. For example, using |
| 2236 | ``bitbake-dumpsigs`` allows you to examine the ``do_compile`` task's | 2236 | ``bitbake-dumpsig`` allows you to examine the ``do_compile`` task's |
| 2237 | "sigdata" for a C application (e.g. ``bash``). Running the command also | 2237 | "sigdata" for a C application (e.g. ``bash``). Running the command also |
| 2238 | reveals that the "CC" variable is part of the inputs that are hashed. | 2238 | reveals that the "CC" variable is part of the inputs that are hashed. |
| 2239 | Any changes to this variable would invalidate the stamp and cause the | 2239 | Any changes to this variable would invalidate the stamp and cause the |