| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| debianization/manpage.patch | manpage updates/fixes | Daniel Echeverry <epsilon77@gmail.com> | yes | |||
| debianization/sandbox.patch | debian specific instructions when no working sandbox is available | Michael Gilbert <mgilbert@debian.org> | no | |||
| debianization/master-preferences.patch | search for {initial,master}_preferences in /etc/chromium The default chromium behavior of checking the current binary directory for initial_preferences or master_preferences doesn't conform to debian policy. |
Andres Salomon <dilinger@debian.org> | no | |||
| debianization/clang-version.patch | hardcode lld for whatever version of clang we're using Upstream doesn't allow overridding the linker name (other than toggling lld vs gold). |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/ps-print.patch | add postscript (ps) printing capability | Salvatore Bonaccorso | no | |||
| fixes/widevine-revision.patch | set widevine version as undefined | Michael Gilbert <mgilbert@debian.org> | no | |||
| fixes/widevine-locations.patch | try alternative locations for libwidevinecdm.so - $HOME/.local/lib/ (snap-friendly, see https://launchpad.net/bugs/1738149) | Olivier Tilloy <olivier.tilloy@canonical.com> | no | |||
| fixes/rust-clanglib.patch | Rust adds some new clang dependencies; specifically: This is in the libclang-rt-14-dev package, but with a different (and architecture-specific) path. So we special-case linux instead of doing the same thing that upstream does w/ chromeos. |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/material-utils.patch | ./../third_party/material_color_utilities/src/cpp/palettes/tones.cc:59:27: note: use function 'std::abs' instead double smallest_delta = abs(smallest_delta_hct.get_chroma() - chroma); ^~~ std::abs ../../third_party/material_color_utilities/src/cpp/palettes/tones.cc:70:9: error: use of undeclared identifier 'round' if (round(chroma) == round(smallest_delta_hct.get_chroma())) { ^ |
no | ||||
| fixes/perfetto.patch | More simple build fixes needed by libstdc++-dev 13 | Andres Salomon <dilinger@debian.org> | no | |||
| fixes/blink-frags.patch | More libstdc++13 build fixes. This should go upstream. | no | ||||
| fixes/v8-compressed-ptrs.patch | Upstream bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1487855 The upstream commit https://chromium-review.googlesource.com/c/v8/v8/+/4753150 introduced a build failure on armhf. I suspect this is what was intended, but we'll see what upstream says. |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/absl-optional.patch | work around a clang bug with libstdc++ Chromium 119 used absl's 'optional' implementation. Chromium 120 switched to aliasing absl::optional to std::optional. In theory that should be all fine and good, except for the fact that there's a bug in clang: https://github.com/llvm/llvm-project/issues/50248 This bug is worked around in libc++, but not in libstdc++. There's (so far) two types of errors we hit. The first is specifically with absl::optional::emplace() - >> gen/ui/gfx/x/randr.cc:482:13: error: no matching member function for call to 'emplace' >> data.lc.emplace(); >> ~~~~~~~~^~~~~~~ >> /usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/optional:914:2: note: candidate template ignored: requirement 'is_constructible_v<x11::RandR::NotifyEvent::Lc>' was not satisfied [with _Args = <>] >> emplace(_Args&&... __args) >> ..and a similar error with just a few calls to absl::make_optional() - >> ./../third_party/blink/renderer/core/loader/history_item.cc:185:19: error: no matching function for call to 'make_optional' >> view_state_ = absl::make_optional<ViewState>(); We can't simply revert to using absl's optional implmentation, because a) they are planning to remove it (<https://abseil.io/about/design/dropin-types>), and b) chromium devs, having switched over and viewing absl::optional and std::optional as aliases, play fast and loose with those namespace. We end up playing an ever-worsening game of whack-a-mole trying to fix build errors which are just inability to do implicit conversions. Another option (which some other distributions have chosen to do) is to simply switch to building against libc++. However, that means bundling a bunch more libraries that build statically against libc++. That's undesirable. This patch provides the option of providing a workaround for libstdc++. Instead of using the official libstdc++ header for optional, we provide our own with the is_constructible assertions removed. There's no logic changes, it just removes an assertion we _know_ is met, but the compiler too broken to know it. I just copied over /usr/include/c++/13/optional, and changed a few of the functions (where you see an '#if 0' commenting out the original function). We'll need to update this patch with major libstdc++ upgrades. |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/libxml-parseerr.patch | ../../third_party/blink/renderer/core/xml/xsl_style_sheet_libxslt.cc:125:26: error: no matching constructor for initialization of 'XMLDocumentParserScope' XMLDocumentParserScope scope(OwnerDocument(), XSLTProcessor::GenericErrorFunc, ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../third_party/blink/renderer/core/xml/parser/xml_document_parser_scope.h:41:3: note: candidate constructor not viable: no known conversion from 'void (void *, const xmlError *)' (aka 'void (void *, const _xmlError *)') to 'xmlStructuredErrorFunc' (aka 'void (*)(void *, _xmlError *)') for 3rd argument XMLDocumentParserScope(Document*, ^ ../../third_party/blink/renderer/core/xml/parser/xml_document_parser_scope.h:40:12: note: candidate constructor not viable: requires 1 argument, but 4 were provided explicit XMLDocumentParserScope(Document*); ^ Not sure why this got changed in chromium, maybe they're using libxml from git? But we change it back. |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/std-to-address.patch | no | |||||
| fixes/stdint.patch | no | |||||
| upstream/mojo.patch | copy of missing files in content/test/data, taken from upstream git This is just cp chromium-git/content/test/data/*{html,mojom,js,ts} \ chromium-debian/content/test/data/ Upstream bug report about the missing files: https://bugs.chromium.org/p/chromium/issues/detail?id=1293630 I'm not sure how much of them are actually needed, but it's easier to just copy all of them for now. Hopefully this will be fixed upstream shortly. This copy is from chromium 120.0.6099.62. |
no | ||||
| upstream/vector.patch | commit ea4397ee3a3b7b324eb1ef8c90c877ef9db226df IWYU: missing include for vector usage in crypto/hkdf.h Bug: 957519 Change-Id: Ia96e2d0ee13b2f682aaae8c05381a7413815bd43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5138462 Reviewed-by: Adam Langley <agl@chromium.org> Commit-Queue: Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/main@{#1239774} diff --git a/crypto/hkdf.h b/crypto/hkdf.h index c9aeabe2b6f8f..8fef8c6d257d5 100644 |
Jose Dapena Paz <jdapena@igalia.com> | no | 2023-12-20 | ||
| upstream/display-header.patch | This fixes: ../../ui/display/types/display_color_management.h:36:8: error: no type named 'string' in namespace 'std' std::string ToString() const; ~~~~~^ Upstream included it in a much larger patch, but we just need the header. |
no | ||||
| upstream/bitset.patch | no | |||||
| upstream/once_flag.patch | commit 3d46966271228714a7948c5cf9eecf2b0d0f2723 IWYU: usage of std::once_flag requires include in simple_font_data.h Bug: 957519 Change-Id: I28253abe5673beb786593a237cfcc7bdc44b1e89 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5140526 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Jos Dapena Paz <jdapena@igalia.com> Cr-Commit-Position: refs/heads/main@{#1240254} diff --git a/third_party/blink/renderer/platform/fonts/simple_font_data.h b/third_party/blink/renderer/platform/fonts/simple_font_data.h index d661e6cd3e8ca..6b74a4eb8b9de 100644 |
Jose Dapena Paz <jdapena@igalia.com> | no | 2023-12-21 | ||
| disable/tests.patch | no | |||||
| disable/unrar.patch | disable support for safe browsing inspection of rar files | Andres Salomon <dilinger@debian.org> | invalid | upstream | ||
| disable/signin.patch | disable browser sign-in | no | https://raw.githubusercontent.com/Eloston/ungoogled-chromium/master/resources/patches/ungoogled-chromium/disable-signin.patch | |||
| disable/android.patch | disable dependency on chrome/android | Michael Gilbert <mgilbert@debian.org> | no | |||
| disable/catapult.patch | remove dependencies on third_party catapult See https://bugs.debian.org/922431 for more details, but tl;dr: we should bring this back and just get rid of the (common) minified stuff in catapult/third_party/. Stuff like chai, jszip, and node-d3 are packaged for debian already. |
Michael Gilbert <mgilbert@debian.org> | no | |||
| disable/font-tests.patch | disable building font tests | Michael Gilbert <mgilbert@debian.org> | no | |||
| disable/swiftshader.patch | avoid building the swiftshader library | Michael Gilbert <mgilbert@debian.org> | no | |||
| disable/swiftshader-2.patch | additional swiftshader stuff exposed by official builds | Andres Salomon <dilinger@debian.org> | no | |||
| disable/google-api-warning.patch | disable the google api key warning when those aren't found | Michael Gilbert <mgilbert@debian.org> | no | |||
| disable/third-party-cookies.patch | disable third-party cookies by default This is easily configured in Settings -> Security & Privacy -> Cookies & other site data With this patch, we just change the default on a new chromium profile. |
Andres Salomon <dilinger@debian.org> | no | |||
| disable/driver-chrome-path.patch | Disable usage of google-chrome in driver | Michel Le Bihan <michel@lebihan.pl> | no | |||
| disable/widevine-cdm-cu.patch | Disable Widevine CDM component updater | Michel Le Bihan <michel@lebihan.pl> | no | |||
| disable/angle-perftests.patch | Disable ANGLE perftests | Michel Le Bihan <michel@lebihan.pl> | no | |||
| disable/clang-version-check.patch | remove strict clang version check during config Chromium 107 has a strict clang version check, added in commit 8f23a2c2d14fd799813134e995c160354d75d3a0. This needs a proper fix upstream; some way to check (or specify) whether it's a distribution build, and therefore shouldn't require a particular git version of clang. For now, let's just get this building in debian. |
Andres Salomon <dilinger@debian.org> | no | |||
| system/icu-shim.patch | allow building against system icu even when is_offical_build=true I noticed this when switching to an official build and trying to build against the system's libicu, but it may be necessary for other system libs as well. If we switch to using the bundled icu, we can see if it's possible to get rid of it. |
Andres Salomon <dilinger@debian.org> | no | |||
| system/jpeg.patch | use system jpeg library | Michael Gilbert <mgilbert@debian.org> | no | |||
| system/zlib.patch | use system zlib library instead of embedded lzma in courgette | Michael Gilbert <mgilbert@debian.org> | no | |||
| system/event.patch | use system libevent | Michael Gilbert <mgilbert@debian.org> | no | |||
| system/openjpeg.patch | no | |||||
| system/clang-format.patch | no | |||||
| system/opus.patch | no | |||||
| system/eu-strip.patch | no | |||||
| system/rapidjson.patch | build against debian's rapidjson-dev package Due to some questionable licensing (the JSON "do not use this for evil" license), debian deletes all of third_party/angle/third_party/rapidjson even though a small portion of it falls under that license. The library is tiny and doesn't change much, so this lets chromium build against the system's rapidjson-dev header files. |
Andres Salomon <dilinger@debian.org> | no | |||
| system/rollup.patch | include debian node libs (needed for rollup) This is strictly just needed for bullseye's rollup , but may be useful later on when we drop more nodejs stuff. =================================================================== |
Andres Salomon <dilinger@debian.org> | no | |||
| bookworm/clang16.patch | This is some clang-18 stuff. For clang-16, the compiler chokes on these flags. These used to only be enabled when llvm_force_head_revision=true, but now they're enabled unconditionally. |
Andres Salomon <dilinger@debian.org> | no | |||
| bookworm/generate-ninja.patch | Bookworm's older gn (generate-ninja) doesn't understand the "mnemonic" variable. Since that string is used by tests that we delete, it doesn't matter anyways. =================================================================== |
Andres Salomon <dilinger@debian.org> | no | |||
| bookworm/freetype-COLRV1.patch | Freetype 2.12 wasn't supposed to have COLRV1 enabled, but it was enabled in bookworm. Then the maintainer issued a stable update to disable it, which caused chromium to crash because we're actually using it. But apparently we're not supposed to be, so drop this version check and always disable COLRV1. This patch is only appropriate for bookworm. See https://bugs.debian.org/1052455 for the description about freetype 2.12 having a broken COLRV1. |
Andres Salomon <dilinger@debian.org> | no | |||
| bookworm/constcountrycode.patch | Work around the following with libstdc++ 12: ./../components/autofill/core/browser/data_model/autofill_i18n_api.h:18:30: error: constexpr variable 'kLegacyHierarchyCountryCodeString' must be initialized by a constant expression constexpr inline std::string kLegacyHierarchyCountryCodeString{"XX"}; ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ =================================================================== |
Andres Salomon <dilinger@debian.org> | no | |||
| bookworm/undo-rust-req.patch | Revert the following patch so that we don't actually need rust to build. commit bcf739b95713071687ff25010683248de0092f6a Remove `enable_rust_qr` build flag. QR code generator implemented in Rust has shipped to Windows, MacOS, Linux, and Android (see https://crrev.com/c/5061588) and is launching to ChromeOS. This means that soon Rust toolchain will be required to build QR support in Chrome - this CL makes an early, small step in this direction by removing the `enable_rust_qr` build flag. Removing the `enable_rust_qr` build flag is a prerequisite for removing the C++ implementation of the QR code generator. Removal of the C++ implementation will not happen until ChromeOS launch process completes (hopefully in a month or so) but removing the `enable_rust_qr` build flag early should help to flush out any potential issues early (e.g. help to identify places where Rust toolchain needs to be added in third-party builds of Chromium). Bug: 1431991 Change-Id: Ib612b96c153c0d311ce6c31ae0415a67c1a3f6a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5064208 Reviewed-by: danakj <danakj@chromium.org> Commit-Queue: ukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/main@{#1229679} =================================================================== |
Lukasz Anforowicz <lukasza@chromium.org> | no | 2023-11-28 | ||
| bookworm/eraseif-lamba.patch | Revert parts of the following two commits, which libstdc++-dev 12 doesn't like In file included from ../../net/http/http_auth_cache.cc:5: In file included from ../../net/http/http_auth_cache.h:11: In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/map:64: /usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/bits/erase_if.h:59:10: error: no matching function for call to object of type '(lambda at ../../net/http/http_auth_cache.cc:92:27)' if (__pred(*__iter)) ^~~~~~ /usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/map:111:24: note: in instantiation of function template specialization 'std::__detail::__erase_nodes_if<std::multimap<net::HttpAuthCache::EntryMapKey, net::HttpAuthCache::Entry>, std::multimap<net::HttpAuthCache::EntryMapKey, net::HttpAuthCache::Entry>, (lambda at ../../net/http/http_auth_cache.cc:92:27)>' requested here return __detail::__erase_nodes_if(__cont, __ucont, __pred); ^ ../../net/http/http_auth_cache.cc:92:8: note: in instantiation of function template specialization 'std::erase_if<net::HttpAuthCache::EntryMapKey, net::HttpAuthCache::Entry, std::less<net::HttpAuthCache::EntryMapKey>, std::allocator<std::pair<const net::HttpAuthCache::EntryMapKey, net::HttpAuthCache::Entry>>, (lambda at ../../net/http/http_auth_cache.cc:92:27)>' requested here std::erase_if(entries_, [](EntryMap::value_type& entry_map_pair) { ^ ../../net/http/http_auth_cache.cc:92:27: note: candidate function not viable: 1st argument ('const std::pair<const net::HttpAuthCache::EntryMapKey, net::HttpAuthCache::Entry>') would lose const qualifier std::erase_if(entries_, [](EntryMap::value_type& entry_map_pair) { ^ ../../net/http/http_auth_cache.cc:92:27: note: conversion candidate of type 'bool (*)(EntryMap::value_type &)' (aka 'bool (*)(pair<const net::HttpAuthCache::EntryMapKey, net::HttpAuthCache::Entry> &)') In file included from ../../net/http/http_auth_cache.cc:5: In file included from ../../net/http/http_auth_cache.h:11: In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/map:64: /usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/bits/erase_if.h:59:10: error: no matching function for call to object of type '(lambda at ../../net/http/http_auth_cache.cc:316:27)' if (__pred(*__iter)) ^~~~~~ /usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/map:111:24: note: in instantiation of function template specialization 'std::__detail::__erase_nodes_if<std::multimap<net::HttpAuthCache::EntryMapKey, net::HttpAuthCache::Entry>, std::multimap<net::HttpAuthCache::EntryMapKey, net::HttpAuthCache::Entry>, (lambda at ../../net/http/http_auth_cache.cc:316:27)>' requested here return __detail::__erase_nodes_if(__cont, __ucont, __pred); ^ ../../net/http/http_auth_cache.cc:316:8: note: in instantiation of function template specialization 'std::erase_if<net::HttpAuthCache::EntryMapKey, net::HttpAuthCache::Entry, std::less<net::HttpAuthCache::EntryMapKey>, std::allocator<std::pair<const net::HttpAuthCache::EntryMapKey, net::HttpAuthCache::Entry>>, (lambda at ../../net/http/http_auth_cache.cc:316:27)>' requested here std::erase_if(entries_, [begin_time, end_time, ^ ../../net/http/http_auth_cache.cc:316:27: note: candidate function not viable: 1st argument ('const std::pair<const net::HttpAuthCache::EntryMapKey, net::HttpAuthCache::Entry>') would lose const qualifier std::erase_if(entries_, [begin_time, end_time, ^ 2 errors generated. commit eb8d184f1b4e236f186cf0619ad03a6847e37758 [base] Remove base::Erase()/base::EraseIf() overloads for std::multimap They're now replaced with C++20 std::erase()/std::erase_if(). Change-Id: I3f6b53e50fb9f69d5b03207fd357b8222c43cd86 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5054086 Owners-Override: Kyle Charbonneau <kylechar@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceac count.com> Reviewed-by: Kyle Charbonneau <kylechar@chromium.org> Commit-Queue: Andrew Rayskiy <greengrape@google.com> Cr-Commit-Position: refs/heads/main@{#1228828} commit be08b98b112a714108c7cbbff94fde5959f4dd1c [base] Remove base::Erase()/base::EraseIf() overloads for std::list They're now replaced with C++20 std::erase()/std::erase_if(). Bug: 1414639 Change-Id: I2f38a845f132bb4115563547f3669f79b7b6c7ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5049925 Commit-Queue: Andrew Rayskiy <greengrape@google.com> Reviewed-by: Kyle Charbonneau <kylechar@chromium.org> Owners-Override: Kyle Charbonneau <kylechar@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1228003} =================================================================== |
Andrew Rayskiy <greengrape@google.com> | no | 2023-11-22 | ||
| bookworm/constexpr-equality.patch | clang-16 workaround ../../components/performance_manager/resource_attribution/query_params.h:30:21: error: return type for defaulted equality comparison operator must be 'bool', not 'const bool' friend const bool operator==(const QueryParams&, ~~~~ ^ I thought we were done with constexpr workarounds after upgrading to clang-16, but apparently we still have some issues with the equality operator. |
Andres Salomon <dilinger@debian.org> | no | |||
| bookworm/nvt.patch | Revert the following (needed for clang-16): commit 940af9f2c87b436559b97c53763aa9eaaf1254eb Use C++20 features to simplify blink::NativeValueTraitsBase. These allow some of the metaprogramming bits to be simplified a little. Change-Id: I052b4397586d21348401616e1792afdb9662f975 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5030335 Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/main@{#1224978} |
Jeremy Roman <jbroman@chromium.org> | no | 2023-11-15 | ||
| ungoogled/disable-privacy-sandbox.patch | disable Privacy Sandbox completely https://github.com/ungoogled-software/ungoogled-chromium/blob/master/patches/core/ungoogled-chromium/disable-privacy-sandbox.patch |
no | ||||
| i386/support-i386.patch | don't disable i386 builds on linux https://chromium-review.googlesource.com/c/chromium/src/+/3583780 Chromium upstream decided to kill off i386 builds on Linux. They were goin to add a 'force_x86_support' arg, but instead "[distributions that still support i386] can patch the file." At this point, i386 on linux is completely unsupported upstream, so we're on our own with bugs. |
Andres Salomon <dilinger@debian.org> | no | |||
| i386/angle-lockfree.patch | revert compile-time lockfree check; switch back to a runtime check. This reverts the following: "commit ce8ce6f81eff8a84e2ea59930cb995b1107181e2 (origin/chromium/5572) Remove ASSERT from AtomicSerial, use static_assert ASSERT is not constexpr, while the AtomicSerial constructor was. This would cause compile errors. Bug: angleproject:7989 Change-Id: Ib6a438d4c055378d4f2f667285b0d2e99f2522ad Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/4205892 " The problem is that this is a compile-time check to ensure that a std::atomic<uint64_t> doesn't require a mutex, but for i386 we can't guarantee that; instead, i386 checks at runtime for the relevant CPU instructions. So we need to revert back to a runtime assertion. Since this is in ANGLE rather than Chromium, hopefully there's a chance they'll take a fix upstream; probably a revert combined with dropping the "constexpr". |
Kimmo Kinnunen <kkinnunen@apple.com> | no | 2023-01-31 | ||
| ppc64le/sandbox/0001-linux-seccomp-bpf-ppc64-glibc-workaround-in-SIGSYS-h.patch | [PATCH] linux/seccomp-bpf: ppc64+glibc workaround in SIGSYS handler Workaround for an apparent issue with glibc negating syscall parameters. Observed on a ppc64le machine with glibc. More investigation required. |
Shawn Anastasio <shawn@anastas.io> | no | 2019-01-15 | ||
| ppc64le/sandbox/0001-sandbox-Enable-seccomp_bpf-for-ppc64.patch | [PATCH 1/1] sandbox: Enable seccomp_bpf for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0001-services-service_manager-sandbox-linux-Fix-TCGETS-de.patch | [PATCH] services/service_manager/sandbox/linux: Fix TCGETS declaration on PPC64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-10 | ||
| ppc64le/sandbox/0001-sandbox-linux-bpf_dsl-Update-syscall-ranges-for-ppc6.patch | [PATCH 1/4] sandbox/linux/bpf_dsl: Update syscall ranges for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0001-sandbox-linux-Implement-partial-support-for-ppc64-sy.patch | [PATCH] sandbox/linux: Implement partial support for ppc64 syscalls and ucontext Unlike other architectures, the ppc64 files currently rely on applicable headers being provided by the system. It is sufficient for standard GNU/Linux environments, but may require expansion elsewhere. |
Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0001-sandbox-linux-Update-IsSyscallAllowed-in-broker_proc.patch | [PATCH] sandbox/linux: Update IsSyscallAllowed in broker_process.cc | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-10-23 | ||
| ppc64le/sandbox/0001-sandbox-linux-Update-syscall-helpers-lists-for-ppc64.patch | [PATCH] sandbox/linux: Update syscall helpers/lists for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-09-18 | ||
| ppc64le/sandbox/0002-sandbox-linux-bpf_dsl-Modify-seccomp_macros-to-add-s.patch | [PATCH 1/4] sandbox/linux/bpf_dsl: Modify seccomp_macros to add support for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0003-sandbox-linux-system_headers-Update-linux-seccomp-he.patch | [PATCH 3/4] sandbox/linux/system_headers: Update linux seccomp header for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0004-sandbox-linux-system_headers-Update-linux-signal-hea.patch | [PATCH 4/4] sandbox/linux/system_headers: Update linux signal header for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0005-sandbox-linux-seccomp-bpf-Add-ppc64-syscall-stub.patch | [PATCH] sandbox/linux/seccomp-bpf: Add ppc64 syscall stub | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0005-sandbox-linux-update-unit-test-for-ppc64.patch | [PATCH 5/6] sandbox/linux: update unit test for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-09-13 | ||
| ppc64le/sandbox/0006-sandbox-linux-disable-timedwait-time64-ppc64.patch | =================================================================== | no | ||||
| ppc64le/sandbox/0007-sandbox-linux-add-ppc64-stat.patch | =================================================================== | no | ||||
| ppc64le/sandbox/Sandbox-linux-services-credentials.cc-PPC.patch | =================================================================== | no | ||||
| ppc64le/sandbox/0008-sandbox-fix-ppc64le-glibc234.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-third_party-angle-Include-missing-header-cstddef-in-.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-Add-PPC64-support-for-boringssl.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-third_party-libvpx-Properly-generate-gni-on-ppc64.patch | [PATCH] third_party/libvpx: Properly generate gni on ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-09-04 | ||
| ppc64le/third_party/0001-third_party-lss-Don-t-look-for-mmap2-on-ppc64.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-third_party-pffft-Include-altivec.h-on-ppc64-with-SI.patch | [PATCH] third_party/pffft: Include altivec.h on ppc64 with SIMD enabled | Shawn Anastasio <shawn@anastas.io> | no | 2019-04-24 | ||
| ppc64le/third_party/0002-third_party-lss-kernel-structs.patch | =================================================================== | no | ||||
| ppc64le/webrtc/Rtc_base-system-arch.h-PPC.patch | =================================================================== | no | ||||
| ppc64le/crashpad/0002-Include-cstddef-to-fix-build.patch | [PATCH] Include cstddef to fix build size_t is not defined unless cstddef is included. |
Timothy Pearson <tpearson@raptorengineering.com> | no | 2018-08-30 | ||
| ppc64le/third_party/0004-third_party-crashpad-port-curl-transport-ppc64.patch | =================================================================== | no | ||||
| ppc64le/workarounds/HACK-third_party-libvpx-use-generic-gnu.patch | =================================================================== | no | ||||
| ppc64le/workarounds/HACK-debian-clang-disable-skia-musttail.patch | =================================================================== | no | ||||
| ppc64le/libaom/0001-Add-ppc64-target-to-libaom.patch | [PATCH] Add ppc64 target to libaom | Shawn Anastasio <shawnanastasio@gmail.com> | no | 2019-03-10 | ||
| ppc64le/libaom/0001-Add-pregenerated-config-for-libaom-on-ppc64.patch | =================================================================== | no | ||||
| ppc64le/third_party/0002-third_party-libvpx-Remove-bad-ppc64-config.patch | commit 7c7b1255458ab2cd00f2eea4d58a90ff6c13dade FIX =================================================================== |
Timothy Pearson <tpearson@raptorengineering.com> | no | 2024-01-22 | ||
| ppc64le/third_party/0002-third-party-boringssl-add-generated-files.patch | =================================================================== | no | ||||
| ppc64le/third_party/0003-third_party-libvpx-Add-ppc64-generated-config.patch | =================================================================== | no | ||||
| ppc64le/third_party/0003-third_party-ffmpeg-Add-ppc64-generated-config.patch | =================================================================== | no | ||||
| ppc64le/third_party/0004-third_party-libvpx-work-around-ambiguous-vsx.patch | =================================================================== | no | ||||
| ppc64le/third_party/skia-vsx-instructions.patch | =================================================================== | no | ||||
| ppc64le/ffmpeg/0001-Add-support-for-ppc64.patch | [PATCH] Add support for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-09-01 | ||
| ppc64le/breakpad/0001-Implement-support-for-ppc64-on-Linux.patch | [PATCH] Implement support for ppc64 on Linux This patch implements support for the ppc64 architecture on Linux systems. Notable changes include: * Modification of tests to support non-4K page sizes * minidump_writer: Determine size of stack to capture based on page size * dump_writer_common: Introduce member function GetVectorRegisters to ThreadInfo on ppc64 systems. This allows Altivec/VMX registers to be dumped like they are on OS X. linux_ptrace_dumper has been updated to utilize this function along with the ptrace mode NT_PPC_VMX. * processor/exploitability_unittest.cc: Tests were disabled on non-x86 systems. They assume the system objdump is capable of disassembling x86 binaries which is not the case on other architectures. To-do: * tools/linux/md2core has been updated as well, but functionality has not been confirmed and restoration of Altivec/VMX registers has not been implemented Note that proper functionality depends on updates to third_party/LSS that introduce PPC64 support. An in-progress patch that allows breakpad to build and run successfully is available at: https://wiki.raptorcs.com/wiki/Porting/Chromium |
Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-17 | ||
| ppc64le/crashpad/0001-Implement-support-for-PPC64-on-Linux.patch | [PATCH] Implement support for PPC64 on Linux This patch implements support for the PPC64 architecture on Linux hosts. |
Shawn Anastasio <sanastasio@raptorengineering.com> | no | 2018-08-30 | ||
| ppc64le/database/0001-Properly-detect-little-endian-PPC64-systems.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-Force-baseline-POWER8-AltiVec-VSX-CPU-features-when-.patch | [PATCH] Force baseline POWER8 / AltiVec / VSX CPU features when on a PPC64 platform in LE mode | Timothy Pearson <tpearson@raptorengineering.com> | no | 2018-09-21 | ||
| ppc64le/fixes/fix-rustc.patch | allow ppc64le to build by using proper rustc target | Andres Salomon <dilinger@debian.org> | no | |||
| ppc64le/fixes/fix-rust-linking.patch | =================================================================== | no | ||||
| ppc64le/fixes/fix-breakpad-compile.patch | =================================================================== | no | ||||
| ppc64le/fixes/fix-partition-alloc-compile.patch | =================================================================== =================================================================== |
no | ||||
| ppc64le/v8/0002-Add-ppc64-trap-instructions.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-Fix-highway-ppc-hwcap.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-Add-PPC64-support-for-libdav1d.patch | [PATCH] Add PPC64 support for libdav1d | Colin Samples <colin.samples+git@gmail.com> | no | 2019-11-01 | ||
| ppc64le/third_party/0001-Fix-libdav1d-compilation-on-clang-ppc.patch | [PATCH] Fix libdav1d compilation on clang ppc | Colin Samples <colin.samples+git@gmail.com> | no | 2019-12-08 | ||
| ppc64le/sandbox/fix-ppc64-linux-syscalls-headers.patch | =================================================================== | no | ||||
| ppc64le/third_party/0003-thirdparty-fix-dav1d-gn.patch | =================================================================== | no | ||||
| ppc64le/third_party/use-sysconf-page-size-on-ppc64.patch | =================================================================== | no | ||||
| ppc64le/third_party/dawn-fix-typos.patch | =================================================================== | no | ||||
| ppc64le/third_party/dawn-fix-ppc64le-detection.patch | =================================================================== | no | ||||
| ppc64le/fixes/fix-unknown-warning-option-messages.diff | =================================================================== | no | ||||
| ppc64le/third_party/0002-Highway-disable-128-bit-vsx.patch | =================================================================== | no |