зеркало из https://github.com/mozilla/gecko-dev.git
f1dcc7b8db
One of the last remaining differences when building Firefox on Debian with all the changes we've done so far is that linking against the system libc statically links some CRT objects. This causes massive differences in the resulting binaries because of slight differences in those objects (because they weren't compiled with the same compiler and because they're not for the exact same glibc version) In practice, their content difference don't cause any problem. If they did, we wouldn't be able to run our builds on newer systems than those we build them on. The only hypothetical risk would be to run on systems with a glibc older than Debian 7's, but those already can't run Firefox anyways (those systems don't have Gtk+3, which is a system requirement). AFAICT, this is only an hypothetical problem anyways, even such systems with Gtk+3 should be able to run those builds. Plus, this is a change that will happen anyways when switching to Debian-based build images, since they would be using the CRT objects from there. We're merely making it happen earlier so that the differences from switching to Debian-based build images are more tractable. Note we only do this when building GCC on Debian, allowing to roll back to CentOS-based toolchains by just switching back the toolchain jobs to use the desktop-build docker image again. |
||
---|---|---|
.. | ||
07F3DBBECC1A39605078094D980C197698C3739D.key | ||
7F74F97C103468EE5D750B583AB00996FC26A641.key | ||
33C235A34C46AA3FFB293709A328C3A2C3C45C06.key | ||
343C2FF0FBEE5EC2EDBEF399F3599FF828C67298.key | ||
13975A70E63C361C73AE69EF6EEB81F8981C74C7.key | ||
AD17A21EF8AED8F1CC02DBD9F7D5C9BF765C61E3.key | ||
EAF1C276A747E9ED86210CBAC3126D3B4AE55E93.key | ||
PR64905.patch | ||
build-gcc.sh | ||
download-tools.sh |