update epel7-erase-fix patch

epel8
Tom spot Callaway 4 years ago
parent f118837e7f
commit b40f3db72f

@ -0,0 +1,20 @@
diff -up chromium-91.0.4472.114/components/ui_devtools/views/view_element.cc.erase-fix chromium-91.0.4472.114/components/ui_devtools/views/view_element.cc
--- chromium-91.0.4472.114/components/ui_devtools/views/view_element.cc.erase-fix 2021-06-28 13:47:06.751802159 -0400
+++ chromium-91.0.4472.114/components/ui_devtools/views/view_element.cc 2021-06-28 13:47:20.097876929 -0400
@@ -24,14 +24,14 @@ namespace {
// Remove any custom editor "prefixes" from the property name. The prefixes must
// not be valid identifier characters.
void StripPrefix(std::string& property_name) {
- auto cur = property_name.cbegin();
+ auto cur = property_name.begin();
for (; cur < property_name.cend(); ++cur) {
if ((*cur >= 'A' && *cur <= 'Z') || (*cur >= 'a' && *cur <= 'z') ||
*cur == '_') {
break;
}
}
- property_name.erase(property_name.cbegin(), cur);
+ property_name.erase(property_name.begin(), cur);
}
ui::EventType GetMouseEventType(const std::string& type) {

@ -332,7 +332,7 @@ Patch108: 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> >&)' # 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); # 33 | property_name.erase(property_name.cbegin(), cur);
# Not sure how this EVER worked anywhere, but it only seems to fail on EPEL-7. # Not sure how this EVER worked anywhere, but it only seems to fail on EPEL-7.
Patch109: chromium-90.0.4430.93-epel7-erase-fix.patch Patch109: chromium-91.0.4472.114-epel7-erase-fix.patch
# Again, not sure how epel8 is the only one to hit this... # Again, not sure how epel8 is the only one to hit this...
# AARCH64 neon symbols need to be prefixed too to prevent multiple definition issue at linktime # AARCH64 neon symbols need to be prefixed too to prevent multiple definition issue at linktime
Patch110: chromium-90.0.4430.93-epel8-aarch64-libpng16-symbol-prefixes.patch Patch110: chromium-90.0.4430.93-epel8-aarch64-libpng16-symbol-prefixes.patch

Loading…
Cancel
Save