same information as <filename>sigdata</filename> files.
</para></listitem>
<listitem><para>
- Run <filename>bitbake-dumpsigs</filename> on the
+ Run <filename>bitbake-dumpsig</filename> on the
<filename>sigdata</filename> or
<filename>siginfo</filename> file.
Here is an example:
<literallayout class='monospaced'>
- $ bitbake-dumpsigs ${BUILDDIR}/tmp/stamps/i586-poky-linux/db/6.0.30-r1.do_fetch.sigdata.7c048c18222b16ff0bcee2000ef648b1
+ $ bitbake-dumpsig ${BUILDDIR}/tmp/stamps/i586-poky-linux/db/6.0.30-r1.do_fetch.sigdata.7c048c18222b16ff0bcee2000ef648b1
</literallayout>
In the output of the above command, you will find a line
like the following, which lists all the (inferred) variable
These functions in turn depend on the variables they
reference.
</note>
- The output of <filename>bitbake-dumpsigs</filename> also includes
+ The output of <filename>bitbake-dumpsig</filename> also includes
the value each variable had, a list of dependencies for each
variable, and
<ulink url='&YOCTO_DOCS_BB_URL;#var-BB_HASHBASE_WHITELIST'><filename>BB_HASHBASE_WHITELIST</filename></ulink>
between two versions of a task.
If you call <filename>bitbake-diffsigs</filename> with just one
file, the command behaves like
- <filename>bitbake-dumpsigs</filename>.
+ <filename>bitbake-dumpsig</filename>.
</para>
<para>