src/core/config/linux.pri | 7 7 + 0 - 0 !
1 file changed, 7 insertions(+)

 unbundle yasm using the unbundling script

src/3rdparty/chromium/third_party/pdfium/third_party/BUILD.gn | 61 11 + 50 - 0 !
1 file changed, 11 insertions(+), 50 deletions(-)

 use system lcms2

src/3rdparty/chromium/base/BUILD.gn | 5 3 + 2 - 0 !
src/3rdparty/chromium/base/time/pr_time_unittest.cc | 2 1 + 1 - 0 !
src/3rdparty/chromium/base/time/time.cc | 2 1 + 1 - 0 !
src/3rdparty/chromium/tools/gn/BUILD.gn | 4 4 + 0 - 0 !
src/3rdparty/chromium/tools/gn/bootstrap/bootstrap.py | 3 1 + 2 - 0 !
5 files changed, 10 insertions(+), 6 deletions(-)

 use system nspr prtime

src/3rdparty/chromium/base/BUILD.gn | 3 1 + 2 - 0 !
src/3rdparty/chromium/base/files/file_path.cc | 6 3 + 3 - 0 !
src/3rdparty/chromium/base/json/json_parser.cc | 28 14 + 14 - 0 !
src/3rdparty/chromium/base/json/string_escape.cc | 4 2 + 2 - 0 !
src/3rdparty/chromium/base/strings/pattern.cc | 20 10 + 10 - 0 !
src/3rdparty/chromium/base/strings/string_split.cc | 2 1 + 1 - 0 !
src/3rdparty/chromium/base/strings/string_util.cc | 12 6 + 6 - 0 !
src/3rdparty/chromium/base/strings/utf_string_conversion_utils.cc | 28 14 + 14 - 0 !
src/3rdparty/chromium/content/browser/devtools/devtools_io_context.cc | 4 2 + 2 - 0 !
src/3rdparty/chromium/net/cert/internal/parse_name.cc | 6 3 + 3 - 0 !
src/3rdparty/chromium/net/tools/transport_security_state_generator/BUILD.gn | 3 3 + 0 - 0 !
src/3rdparty/chromium/tools/gn/BUILD.gn | 1 1 + 0 - 0 !
src/3rdparty/chromium/tools/gn/bootstrap/bootstrap.py | 3 1 + 2 - 0 !
src/3rdparty/chromium/ui/base/ime/input_method_chromeos.cc | 1 0 + 1 - 0 !
src/3rdparty/chromium/ui/gfx/utf16_indexing.cc | 4 2 + 2 - 0 !
15 files changed, 63 insertions(+), 62 deletions(-)

 use the system icu utf functions
 We already depend on ICU, so it is useless to copy these functions here.
 I checked the history of that directory, and other than the renames I am
 undoing, there were no modifications at all.

src/core/web_engine_library_info.cpp | 17 0 + 17 - 0 !
1 file changed, 17 deletions(-)

 do not check for icu data file
 quick hack to avoid checking for the nonexistent icudtl.dat and silence the
 resulting warnings - not upstreamable as is because it removes the fallback
 mechanism for the ICU data directory (which is not used in our builds because
 we use the system ICU, which embeds the data statically) completely

src/3rdparty/chromium/tools/gn/BUILD.gn | 21 0 + 21 - 0 !
src/3rdparty/chromium/tools/gn/gn_main.cc | 6 0 + 6 - 0 !
2 files changed, 27 deletions(-)

 disable last_commit_position
 In Debian, we work off of tarballs that aren't Git repositories. We can't
 expect a Git directory to exist in the tarball, so just remove this useless
 function.

src/buildtools/gn.pro | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 print compiler commands when bootstrapping gn

src/3rdparty/chromium/mojo/public/c/system/macros.h | 8 7 + 1 - 0 !
1 file changed, 7 insertions(+), 1 deletion(-)

 solve alignment issues on i386.
 See the patch below for more information.

src/3rdparty/chromium/third_party/pdfium/core/fpdfapi/parser/cpdf_dictionary.cpp | 10 6 + 4 - 0 !
src/3rdparty/chromium/third_party/pdfium/core/fpdfapi/parser/cpdf_dictionary.h | 3 2 + 1 - 0 !
src/3rdparty/chromium/third_party/pdfium/core/fpdfapi/parser/cpdf_reference.cpp | 7 6 + 1 - 0 !
src/3rdparty/chromium/third_party/pdfium/core/fpdfapi/parser/cpdf_reference.h | 3 2 + 1 - 0 !
4 files changed, 16 insertions(+), 7 deletions(-)

 fix getdict methods in cpdf_object descendants
 In commit [1], Qt WebEngine developers backported a change to cpdf_object.h
 that splits GetDict() virtual method into two: const and non-const.
 .
 However, this change was not applied to CPDF_Dictionary and CPDF_Reference
 that are descendant classes of CPDF_Object. So they were missing the non-const
 override, and the method from base class CPDF_Object was used instead (which
 always returns nullptr).
 .
 In upstream PDFium, all files were changed in [2], so the bug was specific to
 Qt WebEngine 5.11 (Chromium 65-based) branch.
 .
 [1]: https://code.qt.io/cgit/qt/qtwebengine-chromium.git/commit/?id=bc188914f3ce1d2c
 [2]: https://pdfium.googlesource.com/pdfium/+/7e28208d26764438

src/3rdparty/chromium/ui/webui/resources/js/jstemplate_compiled.js | 13 13 + 0 - 0 !
1 file changed, 13 insertions(+)

 restore a file that was erroneously excluded from the tarball

configure.json | 10 10 + 0 - 0 !
src/core/core_module.pro | 2 2 + 0 - 0 !
2 files changed, 12 insertions(+)

 don't allow qtwebenginecore to request executable stack
 The Chromium sources contain assembly code that causes the library to
 default to executable stack (the linker requires that *all* .o files
 have a .note.GNU-stack section in order to default to non-executable).
 So add the -z noexecstack linker flag to change the setting.
 .
 The other libraries are not affected.