From e77d2c296e101a8c2d2d503b082214faa783b5d6 Mon Sep 17 00:00:00 2001
From: Nobuyoshi Nakada <nobu@ruby-lang.org>
Date: Fri, 17 Jun 2022 23:33:23 +0900
Subject: [PATCH] Disable maybe-uninitialized warning for gcc 4

It often shows false positive warnings (at least in 4.8).  Newer
versions work well and we can check correct warnings.
---
 configure.ac | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure.ac b/configure.ac
index bebe4f22c8..fb6fd62664 100644
--- a/configure.ac
+++ b/configure.ac
@@ -642,7 +642,7 @@ AS_CASE(["$GCC:${warnflags+set}:${extra_warnflags:+set}:"],
     AS_IF([test $gcc_major -ge 4], [
 	extra_warnflags="$extra_warnflags -Werror=extra-tokens"
     ])
-    AS_IF([test $gcc_major -ge 5 -a $gcc_major -le 6], [
+    AS_IF([test $gcc_major -ge 4 -a $gcc_major -le 6], [
 	extra_warnflags="$extra_warnflags -Wno-maybe-uninitialized"
     ])
     # ICC doesn't support -Werror=