mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-19 16:25:38 +00:00
4bb0df12f2
After a C++ language version bump, It's possible to wind up in situations where we are using a new enough compiler version, but the libstdc++ version in use is not new enough to support new language features: self-compiled clang with system libraries, clang from `mach bootstrap` prior to C++ language version bump (and thus including a new libstdc++ with the boostrapped clang), etc. Previously, such a situation would mean that things would work fine, and then start breaking as soon as new library features started to be used. Let's try to catch the problem earlier, when the update happens, by verifying that the libstdc++ version is at least as new as the GCC version we're requiring. Differential Revision: https://phabricator.services.mozilla.com/D57516 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| android-ndk.configure | ||
| android-sdk.configure | ||
| arm.configure | ||
| bindgen.configure | ||
| checks.configure | ||
| compile-checks.configure | ||
| compilers-util.configure | ||
| flags.configure | ||
| headers.configure | ||
| init.configure | ||
| java.configure | ||
| keyfiles.configure | ||
| lto-pgo.configure | ||
| memory.configure | ||
| node.configure | ||
| old.configure | ||
| pkg.configure | ||
| rust.configure | ||
| toolchain.configure | ||
| tup.configure | ||
| util.configure | ||
| warnings.configure | ||
| windows.configure | ||