Alberto Garcia [Fri, 26 Mar 2021 10:56:39 +0000 (10:56 +0000)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
When building for x86 in a x86_64 host (e.g. with pbuilder) CMake
will set CMAKE_SYSTEM_PROCESSOR to x86_64, and WebKit will assume
that it's a 64-bit build. Let's use the C++ compiler architecture as
a temporary solution to detect x86 correctly.
===================================================================
* Rebuild for buster-security.
* The WebKitGTK security advisory WSA-2021-0002 lists the following
security fixes in the latest versions of WebKitGTK:
+ CVE-2020-9947 (fixed in 2.30.0).
+ CVE-2020-27918, CVE-2020-29623, CVE-2021-1765, CVE-2021-1789,
CVE-2021-1799, CVE-2021-1801, CVE-2021-1870 (fixed in 2.30.6).
* debian/patches/force-single-process.patch:
+ Force the single-process mode in Evolution and Geary
* debian/control:
+ Remove Breaks for Evolution < 3.34.1.
+ Remove build dependency on libwpebackend-fdo-1.0-dev.
+ Switch build dependency from libenchant-2-dev to libenchant-dev.
+ Switch build dependencies on libgl-dev and libgles-dev with
libgl1-mesa-dev and libgles2-mesa-dev.