Bug 6520 - QA Issue: Architecture did not match (3 to 62)
Summary: QA Issue: Architecture did not match (3 to 62)
Status: RESOLVED NOTABUG
Alias: None
Product: Other YP Layers
Classification: Build System, Metadata & Runtime
Component: layers (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: Future
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-07-09 17:35 UTC by Leah
Modified: 2014-07-10 14:51 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leah 2014-07-09 17:35:13 UTC
I have a recipe located at https://github.com/wolfSSL/meta-wolfssl/tree/master/recipes-wolfssl/benchmark which will not build with bitbake. I am getting a QA Issue: Architecture did not match error and can't seem to debug my problem. This is only the second recipe I have written, so I am not sure where exactly my problem lies. 

The output (I can add the detailed error log if needed):

ERROR: QA Issue: Architecture did not match (3 to 62) on /work/core2-32-poky-linux/benchmark/3.0.0-r1/packages-split/benchmark-dbg/usr/bin/.debug/benchmark
ERROR: QA Issue: Architecture did not match (3 to 62) on /work/core2-32-poky-linux/benchmark/3.0.0-r1/packages-split/benchmark/usr/bin/benchmark
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa


Any help in determining how to correct the differing architectures, or whatever might be causing this error, would be greatly appreciated. 

Thanks,

Leah
Comment 1 Leah 2014-07-09 21:09:37 UTC
I fixed it. I somehow had 2 executables, one in ${WORKDIR} and one in ${WORKDIR}/${PN}-${PV} and was using the one in workdir instead of the workdir/pn-pv one. I changed this and it works perfectly.
Comment 2 Saul Wold 2014-07-10 14:51:22 UTC
based on the comments, this appears to be a non-core layer and recipe, which you seem to have fixed so I am closing this as not a bug.