4215 2013-04-07 20:52:05 +0000 meta-intel: openssl-qat-module.bb build error under multilib 2013-04-10 20:24:08 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-meta-intel unspecified x86 x86_64 RESOLVED DUPLICATE 4126 Medium+ normal 1.4 M6 1 peterlei alexandru.damian alexandru.damian kishore.k.bodke nitin.a.kamble sgw tom.zanussi --- --- --- oldest_to_newest 31647 0 peterlei 2013-04-07 20:52:05 +0000 I'm building core-image-sato for crystalforest-gladden with multilib:lib32 enabled and see this build error: > ERROR: QA Issue: non debug package contains .debug directory: openssl-qat-module path /work/crystalforest_gladden-poky-linux/openssl-qat-module/1.0.1-r0/packages-split/openssl-qat-module/lib64/modules/3.8.4-yocto-standard/kernel/drivers/.debug/qat_mem.ko > ERROR: QA run found fatal errors. Please consider fixing them. > ERROR: Function failed: do_package_qa I effectively added this: require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" I can work around this problem in the recipe by either changing the openssl-qat-module.bb recipe's MODULE_DIR from $base_libdir to $nonarch_base_libdir, or by removing a number of lines to let module.bbclass completely handle the module do_install/packaging instead. The BSP I'm using is meta-crystalforest, currently off of: poky: master 6d4d42d63db4c3fcffd831ce359599f3ee1d710e meta-intel: master c69366c648e7288ea029ffcd59635575c15349ea MACHINE is "crystalforest-gladden" 31812 1 alexandru.damian 2013-04-10 12:53:25 +0000 Patch sent for review. 31847 2 tom.zanussi 2013-04-10 17:10:16 +0000 I think this may be fixed by kishore's earlier patch: https://lists.yoctoproject.org/pipermail/meta-intel/2013-April/000647.html Waiting on kishore to confirm. 31853 3 kishore.k.bodke 2013-04-10 17:53:56 +0000 Yes, This patch is not needed if the below patch is applied. https://lists.yoctoproject.org/pipermail/meta-intel/2013-April/000647.html module.bbclass will handle the module do_install/packaging. Thanks Kishore. 31860 4 tom.zanussi 2013-04-10 20:24:08 +0000 According to Kishore, meta-intel commit e3f78500b1eba6fce602bd146affa868357c2d66 will fix this, so closing accordingly and marking it as a duplicate of 4126. *** This bug has been marked as a duplicate of bug 4126 ***