Changes between Version 3 and Version 4 of WebKitGTK/GCCRequirement

Nov 20, 2017 11:28:46 AM (6 years ago)
Michael Catanzaro



  • WebKitGTK/GCCRequirement

    v3 v4  
    55This policy may mean that a new version of GCC is required sooner than you might prefer. Because Apple does not use GCC to develop WebKit, and because of the relatively high number of compatibility issues caused by supporting GCC, we should be grateful that it is still possible to build WebKit with GCC at all. Unless you are able to upgrade your systems to newer GCCs on a regular basis, it is expected that your system GCC may not be new enough to build WebKit. We urge you to consider building with a custom compiler instead. One option that may sometimes work is to try to build with Clang, which may be new enough when GCC is not. (Clang is the compiler that Apple uses to develop WebKit.) Another option is to bootstrap a newer version of GCC as part of your WebKit build. If you choose to stop building new versions of WebKit as a result of a GCC version increase, rather than bootstrapping a newer compiler, your users will be left vulnerable to numerous security vulnerabilities that are fixed in newer versions.
     7== GCC 4.9 -> GCC 5 ==
     9In very rare cases, a C++ ABI change may make upgrading to a new version of GCC unusually difficult. For example, the C++ ABI changed between GCC 4.9 and GCC 5. Building WebKit with libstdc++ 5 would ordinarily require that you recompile all C++ libraries that it links against using the newer libstdc++. However, in this particular case, a compatibility option is provided: you can configure GCC with --with-default-libstdcxx-abi=gcc4-compatible when building GCC itself. This option may not exist forever, but it appears to still be supported as of libstdc++ 7.