summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-06-27 09:13:12 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-07-03 13:57:10 +0100
commitc74284d5d93ea68302d9a3864cd746e6c4cd47de (patch)
treef0caf80bc261b13db2305dd1b04477689da494d3
parent695946e5ff12382787fadc44bc805e342521befd (diff)
downloadast2050-yocto-poky-c74284d5d93ea68302d9a3864cd746e6c4cd47de.zip
ast2050-yocto-poky-c74284d5d93ea68302d9a3864cd746e6c4cd47de.tar.gz
ref-manual: Some minor fixes to the QA Checks chapter.
* For "Architecture did not match" and "Bit size did not match", added the missing QA check name marker [arch] * Under the already-stripped entry, added a final sentence (to the paragraph before the note box) (From yocto-docs rev: 7c3bda03a4424d1e083403266c570b34fcab9bbf) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/ref-manual/ref-qa-checks.xml11
1 files changed, 9 insertions, 2 deletions
diff --git a/documentation/ref-manual/ref-qa-checks.xml b/documentation/ref-manual/ref-qa-checks.xml
index 43a0bd0..15c1bbe 100644
--- a/documentation/ref-manual/ref-qa-checks.xml
+++ b/documentation/ref-manual/ref-qa-checks.xml
@@ -271,7 +271,7 @@
<listitem>
<para>
<code>
- Architecture did not match (&lt;machine_arch&gt; to &lt;file_arch&gt;) on &lt;file&gt;
+ Architecture did not match (&lt;machine_arch&gt; to &lt;file_arch&gt;) on &lt;file&gt; [arch]
</code>
</para>
@@ -310,7 +310,7 @@
<listitem>
<para>
<code>
- Bit size did not match (&lt;machine_bits&gt; to &lt;file_bits&gt;) &lt;recipe&gt; on &lt;file&gt;
+ Bit size did not match (&lt;machine_bits&gt; to &lt;file_bits&gt;) &lt;recipe&gt; on &lt;file&gt; [arch]
</code>
</para>
@@ -946,11 +946,18 @@
In order for debugging to work on the target using
<filename>-dbg</filename> packages, this stripping must be
disabled.
+ </para>
+
+ <para>
Depending on the build system used by the software being
built, disabling this stripping could be as easy as
specifying an additional configure option.
If not, disabling stripping might involve patching
the build scripts.
+ In the latter case, look for references to "strip" or
+ "STRIP", or the "-s" or "-S" command-line options being
+ specified on the linker command line (possibly
+ through the compiler command line if preceded with "-Wl,").
<note>
Disabling stripping here does not mean that the final
packaged binaries will be unstripped.
OpenPOWER on IntegriCloud