Fix header files to compile libgpg-error-native on ppc64le Power8 build machine

Using a ppc64le build machine the following error occurs when compiling libjpg-error-native

cp: cannot stat '/home/ubuntu/Yocto/build-ppc64/tmp/work/ppc64le-linux/libgpg-error-native/1.32-r0/libgpg-error-1.32/src/syscfg/lock-obj-pub.ppc64le-unknown-linux-gnu.h': No such file or directory

---
 meta/recipes-support/libgpg-error/libgpg-error_1.32.bb | 2 ++
 1 file changed, 2 insertions(+)

index 4f3e3d8..1a8c1dc 100644
@@ -48,6 +48,8 @@ do_compile_prepend() {
 	  mips*el)    TUPLE=mipsel-unknown-linux-gnu ;;
 	  mips*)      TUPLE=mips-unknown-linux-gnu ;;
 	  x86_64)     TUPLE=x86_64-unknown-linux-gnu ;;
+          ppc64le) TUPLE=powerpc64le-unknown-linux-gnu ;;
+          ppc64) TUPLE=powerpc64-unknown-linux-gnu ;;
 	  *)          TUPLE=${TARGET_ARCH}-unknown-linux-gnu ;;
 	esac
 

2.7.4

The identical patch by Serhey Popovych is queued for master right now.

Ross

== Series Details ==

Series: Fix header files to compile libgpg-error-native on ppc64le Power8 build machine
Revision: 1
URL : https://patchwork.openembedded.org/series/14828/
State : failure

== Summary ==

Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:

* Patch            Fix header files to compile libgpg-error-native on ppc64le Power8 build machine
 Issue             Shortlog does not follow expected format [test_shortlog_format] 
  Suggested fix    Commit shortlog (first line of commit message) should follow the format "<target>: <summary>"

* Patch            Fix header files to compile libgpg-error-native on ppc64le Power8 build machine
 Issue             Patch is missing Signed-off-by [test_signed_off_by_presence] 
  Suggested fix    Sign off the patch (either manually or with "git commit --amend -s")

If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).

---

Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe