public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Than Ngo <than@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: added missing chromium-85.0.4183.83-el7-old-libdrm.patch for epel7
Date: Fri, 07 Aug 2026 16:04:37 GMT	[thread overview]
Message-ID: <178611867769.1.13775589913481685520.rpms-chromium-72f760a379cc@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/chromium
Branch : epel9-next
Commit : 72f760a379cc7bb0cb3ecd2338ef73e8ded79dc0
Author : Than Ngo <than@redhat.com>
Date   : 2023-01-27T18:09:45+01:00
Stats  : +20/-0 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/chromium/c/72f760a379cc7bb0cb3ecd2338ef73e8ded79dc0?branch=epel9-next

Log:
added missing chromium-85.0.4183.83-el7-old-libdrm.patch for epel7

---
diff --git a/chromium-85.0.4183.83-el7-old-libdrm.patch b/chromium-85.0.4183.83-el7-old-libdrm.patch
new file mode 100644
index 0000000..d7d7f6e
--- /dev/null
+++ b/chromium-85.0.4183.83-el7-old-libdrm.patch
@@ -0,0 +1,15 @@
+diff -up chromium-85.0.4183.83/ui/gfx/linux/drm_util_linux.cc.el7-old-libdrm chromium-85.0.4183.83/ui/gfx/linux/drm_util_linux.cc
+--- chromium-85.0.4183.83/ui/gfx/linux/drm_util_linux.cc.el7-old-libdrm	2020-08-31 09:38:46.043993882 -0400
++++ chromium-85.0.4183.83/ui/gfx/linux/drm_util_linux.cc	2020-08-31 09:39:21.599906318 -0400
+@@ -6,6 +6,11 @@
+ 
+ #include <drm_fourcc.h>
+ 
++// the libdrm in EL-7 is too old to have this define
++#ifndef DRM_FORMAT_P010
++#define DRM_FORMAT_P010 DRM_FORMAT_INVALID
++#endif
++
+ #include "base/notreached.h"
+ 
+ namespace ui {

diff --git a/chromium.spec b/chromium.spec
index 1c6c843..28085a9 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -341,6 +341,10 @@ Patch103: chromium-99.0.4844.51-epel7-old-headers-workarounds.patch
 # Revert: https://github.com/chromium/chromium/commit/c3213f8779ddc427e89d982514185ed5e4c94e91
 Patch104: chromium-99.0.4844.51-epel7-old-cups.patch
 
+# libdrm on EL7 is rather old and chromium assumes newer
+# This gets us by for now
+Patch105: chromium-85.0.4183.83-el7-old-libdrm.patch
+
 # error: no matching function for call to 'std::basic_string<char>::erase(std::basic_string<char>::const_iterator, __gnu_cxx::__normal_iterator<const char*, std::basic_string<char> >&)'
 #   33 |   property_name.erase(property_name.cbegin(), cur);
 # Not sure how this EVER worked anywhere, but it only seems to fail on EPEL-7.
@@ -1011,6 +1015,7 @@ udev.
 %patch101 -p1 -b .wayland-strndup-error
 %patch103 -p1 -b .epel7-header-workarounds
 %patch104 -p1 -b .el7cups
+%patch105 -p1 -b .el7-old-libdrm
 %patch106 -p1 -b .el7-erase-fix
 %patch107 -p1 -b .el7-extra-operator-equalequal
 %endif

                 reply	other threads:[~2026-08-07 16:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178611867769.1.13775589913481685520.rpms-chromium-72f760a379cc@fedoraproject.org \
    --to=than@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox