openjdk-8: fix build for gcc8.x

Currently oe-core/YoctoProject migrated to gcc8.x. This update broke our
openjdk-8 and openjre-8 build. This patch avoids this problem by disabling
the problematic gcc warnings and errors.

Signed-off-by: Richard Leitner <richard.leitner@skidata.com>

2 files changed, 22 insertions, 0 deletions

diff --git a/recipes-core/openjdk/openjdk-8-release-16xbyy.inc b/recipes-core/openjdk/openjdk-8-release-16xbyy.inc
index bd4a349..7ca0997 100644
--- a/recipes-core/openjdk/openjdk-8-release-16xbyy.inc
+++ b/recipes-core/openjdk/openjdk-8-release-16xbyy.inc
@@ -16,6 +16,7 @@ PATCHES_URI = "\
     file://0008-jdk-use-correct-include-for-signal.patch \
     file://0009-jdk-disable-backtrace-musl-build-fix.patch \
     file://0010-build-fix-build-on-as-needed-toolchains-generic.patch \
+    file://hotspot_fix_gcc8x_build.patch \
 "
 # some patches extracted from http://cr.openjdk.java.net/~rkennke/shark-build-hotspot/webrev.01/hotspot.patch
 # reported via http://mail.openjdk.java.net/pipermail/build-dev/2015-January/013972.html
diff --git a/recipes-core/openjdk/patches-openjdk-8/hotspot_fix_gcc8x_build.patch b/recipes-core/openjdk/patches-openjdk-8/hotspot_fix_gcc8x_build.patch
new file mode 100644
index 0000000..1a406f2
--- /dev/null
+++ b/recipes-core/openjdk/patches-openjdk-8/hotspot_fix_gcc8x_build.patch
@@ -0,0 +1,21 @@
+From: Richard Leitner <richard.leitner@skidata.com>
+Date: Thu, 14 Jun 2018 23:42:11 +0200
+Subject: [PATCH] openjdk-8: hotspot: fix gcc8 compilation
+
+As oe-core/yocto-project master migrated to gcc8.x we need to support this.
+Therefore disable following gcc warnings/errors which caused the build to fail:
+  + stringop-overflow
+  + return-type
+---
+
+--- a/hotspot/make/linux/makefiles/gcc.make
++++ b/hotspot/make/linux/makefiles/gcc.make
+@@ -197,7 +197,7 @@
+ endif
+ 
+ # Compiler warnings are treated as errors
+-WARNINGS_ARE_ERRORS = -Werror
++WARNINGS_ARE_ERRORS = -Werror -Wno-stringop-overflow -Wno-error=return-type
+ 
+ ifeq ($(USE_CLANG), true)
+   # However we need to clean the code up before we can unrestrictedly enable this option with Clang