mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-12-01 17:23:59 +00:00
d651932496
Depending on the compiler you use when --enable-stdcxx-compat, the compiler can know about different libstdc++.so libraries that are not suitable for your target. This will manifest as an assertion in the current libstdcxx.py file. And then, when you change the assertion to actually print out useful information, you will see things like: /bin/ld: skipping incompatible /builds/worker/workspace/build/src/clang/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.9.4/../../../libstdc++.so when searching for -lstdc++ /bin/ld: skipping incompatible /builds/worker/workspace/build/src/clang/bin/../lib/libstdc++.so when searching for -lstdc++ which libstdcxx.py misinterprets as candidates for libstdc++.so. This patch attempts to remedy both situations by providing a more informative error message when things go sideways and also filtering out error messages from the linker. You could argue that perhaps --enable-stdcxx-compat shouldn't be getting set for such builds, but this change seems reasonable enough on its own. |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| l10n/fluent_migrations | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozterm | ||
| mozversioncontrol | ||
| mach_commands.py | ||
| moz.build | ||
| README | ||
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025