use fpermissive on vaapi code on i686

chromium-70.0.3538.110-vaapi-i686-fpermissive.patch

@@ -0,0 +1,24 @@
+diff -up chromium-70.0.3538.110/media/gpu/vaapi/BUILD.gn.i686permissive chromium-70.0.3538.110/media/gpu/vaapi/BUILD.gn
+--- chromium-70.0.3538.110/media/gpu/vaapi/BUILD.gn.i686permissive	2018-11-29 09:27:02.405909871 -0500
++++ chromium-70.0.3538.110/media/gpu/vaapi/BUILD.gn	2018-11-29 09:29:50.648259696 -0500
+@@ -10,6 +10,11 @@ import("//ui/ozone/ozone.gni")
+ 
+ assert(use_vaapi)
+ 
++config("vaapi_permissive") {
++  cflags = [ "-fpermissive" ]
++}
++
++
+ action("libva_generate_stubs") {
+   extra_header = "va_stub_header.fragment"
+ 
+@@ -98,6 +103,8 @@ source_set("vaapi") {
+     "//third_party/libyuv",
+   ]
+ 
++  configs += [ ":vaapi_permissive" ]
++
+   if (use_x11) {
+     configs += [ "//build/config/linux:x11" ]
+     deps += [ "//ui/gfx/x" ]

chromium.spec

@@ -296,6 +296,7 @@ Patch120:	chromium-70.0.3538.110-remove-sysroot-options.patch
 # Enable VAAPI support on Linux
 # NOTE: This patch will never land upstream
 Patch121:	enable-vaapi.patch
+Patch122:	chromium-70.0.3538.110-vaapi-i686-fpermissive.patch
 
 
 # Use chromium-latest.py to generate clean tarball from released build tarballs, found here:
@@ -845,6 +846,9 @@ udev.
 %patch119 -p1 -b .aarch64-new-stat
 %patch120 -p1 -b .sysrootfix
 %patch121 -p1 -b .vaapi
+%ifarch i686
+%patch122 -p1 -b .i686permissive
+%endif
 
 
 # Change shebang in all relevant files in this directory and all subdirectories