Граф коммитов

4566 Коммитов

Автор SHA1 Сообщение Дата
Mike Hommey aadf5fb0df Bug 1278456 - Bump libstdc++ requirement to 3.4.16 (4.6.1). r=froydnj
Similarly to the considerations about glibc, the Linux compatibility matrix
(https://developer.mozilla.org/en-US/Firefox/Linux_compatibility_matrix)
tells us no distro with Gtk+3 3.4 has a version of libstdc++ older than
4.6.

The data in the matrix doesn't go to that level of detail, but Ubuntu
12.04 LTS, being the only one with version 4.6 (others have at least
4.7), it's worth noting it has version 4.6.3. Which means we can safely
require libstdc++ symbols version 3.4.16 (which were added in 4.6.1).

This will allow us to remove a lot of the stdc++ compatibility hacks.
2016-06-12 18:51:32 +09:00
Mike Hommey a898d16968 Bug 1278456 - Bump glibc requirement to 2.12. r=froydnj
The requirement for glibc has been set to version 2.7 for a long while.

Spidermonkey uses the pthread_setname_np symbol, which is only available
since glibc 2.12. So far, we've been fortunate that the symbol doesn't
end up in libxul, or tests that link to js directly, because the symbol
is eliminated as being called by effectively dead code.

There are multiple reasons why this is going to change, one of which
being changes to the way things are linked, that will make the linker
not eliminate that code in some cases. Another is that eventually, the
separation of build systems between js and top-level is going to fade,
and the glibc checks, which apply to all gecko binaries, will also apply
to js binaries. They currently are not happening, and would fail because
of pthread_setname_np if they were.

Taking a step back, as of version 46, the mozilla.org builds require at
least Gtk+3 3.4. Which means the requirements for the underlying system
have received a dramatic bump, and it's time to revisit the requirements
for binary compatibility.

I went through all my notes from all the recent times binary compatibility
has been considered, and put together a compatibility matrix on MDN from
that data as well as more recent data that I could find here and there,
about the major non-rolling-release distros (RHEL, Fedora, SuSE, Debian,
Ubuntu)
https://developer.mozilla.org/en-US/Firefox/Linux_compatibility_matrix

Considering the data there, none of the distros that have at least Gtk+3
3.4 have a glibc older than 2.13. The list of symbols that 2.13 provides
that 2.12 doesn't have is not large enough, though, to really care about
depending on 2.13.
2016-06-12 18:51:23 +09:00
Dustin J. Mitchell eb7f0385b1 Bug 1275409: mock os.path.is{dir,file} too; r=gps
This uses a rough form of prefix matching, considering anything that ends in a
path separator and appears as a prefix of a file to be a directory.

MozReview-Commit-ID: 7FJSxI0fBSA

--HG--
extra : rebase_source : e4cece21a25ac1216d96647963955459d0f964e5
2016-06-05 18:34:31 +00:00
Wes Kocher 807cf956d8 Merge m-c to inbound, a=merge 2016-06-06 17:14:49 -07:00
ffxbld 219956a13e Update configs. IGNORE BROKEN CHANGESETS CLOSED TREE NO BUG a=release ba=release 2016-06-06 15:18:13 -04:00
Dustin J. Mitchell 954a9c8264 Bug 1274611: handle empty error messages properly; r=gps
MozReview-Commit-ID: 4Adn7X0HOu1

--HG--
extra : rebase_source : 435de9993283df8362094f2033e9cf6d627f190e
2016-05-27 22:19:54 +00:00
Makoto Kato dcd9507126 Bug 1277498 - Remove MC (message compiler) define from old-configure.in. r=mshal
By bug 1270621, ETW support is removed.  So no one uses messege compiler.

MozReview-Commit-ID: HGUAkrb208N

--HG--
extra : rebase_source : 5178283b781e4805b4e97f09b35a4150119d060a
extra : histedit_source : 40d6992894315b51863db4e7697df1c1ef18edd8
2016-06-06 13:36:51 +09:00
Mike Hommey 6d9272b820 Bug 1276069 - Change the local variable used in config/external/nss/Makefile.in to pass down as XCFLAGS to NSS build system. r=froydnj
The intent in bug 1271829 was to make all the XCFLAGS set in
config/external/nss/Makefile.in accumulate instead of replacing each
other. Unfortunately, there is also an AC_SUBST variable named XCFLAGS,
use for other purposes, and we ended up adding on top of that variable.

Using a different local variable allows to still accumulate the values,
while keeping away from the XCFLAGS from autoconf.mk.
2016-05-27 13:23:16 +09:00
Dustin J. Mitchell 22bd1fe157 Bug 1272315: mozunit: log error message with line number only if available; r=glandium
MozReview-Commit-ID: 7Ye9RrKw6cw

--HG--
extra : rebase_source : d7ca5d202354f1c95a057abede465583c06b6c45
extra : source : 8b3b9c531a5ef763d2ee1c340aa41af474dd7810
2016-05-24 15:32:39 +00:00
David Keeler e87f6f88e2 bug 1273677 - ensure session cache is properly configured and torn down for TLSServerSocket r=mcmanus
MozReview-Commit-ID: 6i7HxTdLcID

--HG--
extra : rebase_source : 3c1b4c0ed798c166cbc2bcad71de90543af176c1
2016-05-23 13:58:56 -07:00
Mike Hommey 8855262939 Bug 1269171 - Change how mozalloc.h is hooked in STL wrappers. r=froydnj
Since the introduction of the STL wrappers, they have included
mozalloc.h, and multiple times, we've hit header reentrancy problems,
and worked around them as best as we could.

Taking a step back, all mozalloc.h does is:
- declare moz_* allocator functions.
- define inline implementations of various operator new/delete variants.

The first only requires the functions to be declared before they are used,
so mozalloc.h only needs to be included before anything that would use
those functions.

The second doesn't actually require a specific order, as long as the
declaration for those functions comes before their use, and they are
either declared in <new> or implicitly by the C++ compiler.

So all in all, it doesn't matter that mozalloc.h is included before the
wrapped STL headers. What matters is that it's included when STL headers
are included. So arrange things such that mozalloc.h is included after
the first wrapped STL header is fully preprocessed (and all its includes
have been included).
2016-05-22 08:32:40 +09:00
Mike Hommey 60564d7bff Bug 1269171 - Backout ccff1c4580ab (bug 1270832) because it doesn't actually work properly and blocks upcoming changes. r=froydnj
It turns out that, since we're including <new> before setting
_GLIBCXX_DEBUG, the debug parts of c++config.h are not activated, and
that has an impact of how much of the debug features of the STL are
activated.

In contrast, the upcoming changes to the STL wrappers are avoiding the
include of <new> before _GLIBCXX_DEBUG is set, which in turn breaks the
build because, as we link things that use STL wrappers with things that
don't, they end up with a different state of STL debugging, and have
mismatching symbols.
2016-05-22 08:32:33 +09:00
Ralph Giles 49736b0095 Bug 1271829 - Propagate MSVC -arch switch to nss. r=glandium
This updates the nss build to require SSE2 instructions on win32.

By default nss builds with -arch:IA32 for maximum compatibility.
Firefox 49 dropped support for non-SSE2 platforms, so propagate
that to the nss external build. XCFLAGS come after the nss build's
default settings, and the last -arch switch will override the
previous ones.

Bump CLOBBER because we've had trouble with file removal permission
errors on integration builds.

MozReview-Commit-ID: 2lfDq0e0T7Y
2016-05-20 19:35:51 -07:00
Ralph Giles 2e85949c69 Bug 1271829 - Don't clobber XCFLAGS building nss. r=glandium
Previously, this clobbered the XCFLAGS set by MOZ_FOLD_LIBS_FLAGS.
Combine them instead so we can pass multiple options through
this override mechanism.

This is a behaviour change building with --enable-llvm-hacks.

MozReview-Commit-ID: 4WP0asnc7Z6
2016-05-20 19:35:51 -07:00
Wes Kocher 4f7146f46c Backed out changeset 1b8f35a4774e (bug 1273677) for valgring leaks CLOSED TREE 2016-05-20 18:13:12 -07:00
David Keeler a53c0feecf bug 1273677 - ensure session cache is properly configured and torn down for TLSServerSocket r=mcmanus
MozReview-Commit-ID: 6i7HxTdLcID

--HG--
extra : rebase_source : 5a64db198fe582e6057bb58f8f51be3e9a63192b
2016-05-17 15:17:33 -07:00
Martin Thomson 57bd3390d7 Bug 1250568 - Enable building of TLS 1.3, r=ekr
MozReview-Commit-ID: BPaRVGPK7SR

--HG--
extra : rebase_source : 86dc610f3900e1dad2292d23e52dfb11da23492f
2016-04-04 16:21:19 -03:00
Dustin J. Mitchell 0444ac1f2f Bug 1258497: allow mozunit to pass along kwargs; r=gps
MozReview-Commit-ID: DzmF3zF5jeD

--HG--
extra : rebase_source : b8fead11cee6600cbf6ea241e77208f2418007cb
2016-05-09 18:56:24 +00:00
Nathan Froyd ba6687453e Bug 1270832 - turn on debug mode for libstdc++ headers; r=glandium 2016-05-11 17:01:39 -04:00
Nathan Froyd a780b60bd9 Backout fe3f7921e2dc (bug 1270832) because it's going to break Linux static analysis builds; r=me 2016-05-11 10:43:43 -04:00
Nathan Froyd d795a83fd0 Bug 1270832 - turn on debug mode for libstdc++ headers; r=glandium 2016-05-11 10:42:24 -04:00
Ralph Giles df51e79d6e Bug 1268617 - Pass -g to rustc on debug builds. r=ted
Enable debug output from the rust compiler when we're doing so
for the C/C++ compilers.

MozReview-Commit-ID: K0iqlPZ1Thu
2016-05-10 16:15:43 -07:00
Mike Shal 5ab92bb3fa Bug 1252804 - remove TARGET_LOCAL_INCLUDES; r=ted
MozReview-Commit-ID: 6s1SWINNMM9

--HG--
extra : rebase_source : 3c64cc907a41215be454ccae4230d3d216e097d9
2016-04-29 17:09:57 -04:00
Wes Kocher 61d73dfc73 Backed out changeset 6aa3f079d304 (bug 1268617) for debug windows devtools failures on a CLOSED TREE 2016-05-03 15:16:38 -07:00
Ralph Giles 1f7512408c Bug 1268617 - Pass -g to rustc on debug builds. r=ted
Enable debug output from the rust compiler when we're doing so
for the C/C++ compilers.

MozReview-Commit-ID: K0iqlPZ1Thu

--HG--
extra : rebase_source : 21220c0b7eeaa9036346e87d2bd1d475a129920e
2016-04-28 11:56:02 -07:00
Thomas Klausner 001b559468 Bug 1268879 - "complex" header missing from config/system-headers
MozReview-Commit-ID: 61GpVkY5JZS

--HG--
extra : rebase_source : 7d9b6d7e622b209f77ad837f09af4420c41c6afd
2016-05-02 17:27:34 -07:00
Lee Salzman a0a61c0134 Bug 1268816 - allow Skia to use C++11 features on platforms that have them. r=froydnj 2016-04-29 21:03:05 -04:00
ffxbld 50a14b0c3c Update configs. IGNORE BROKEN CHANGESETS CLOSED TREE NO BUG a=release ba=release 2016-04-25 10:10:40 -07:00
David Keeler 1e53398a23 bug 1182742 - allow users to override small key size errors r=rbarnes
Key size enforcement for TLS certificates happens at two levels: PSM and NSS.
PSM enforces a minimum of 1024 bits. NSS enforces a minimum of 1023 bits by
default. The NSS error is not overridable, but the PSM error is. This change
allows users to connect to devices with small RSA keys (as little as 512 bits)
using the certificate error override functionality.

MozReview-Commit-ID: 2TZ8c4I3hXC

--HG--
extra : rebase_source : a9c550f15261c711e789a670c90c129c65802ff0
2016-04-11 13:45:47 -07:00
Nathan Froyd 82c6f5d7a7 Bug 1163224 - add build system support for multiple Rust crates; r=glandium
Our current build system support for Rust compiles any Rust crate into a
so-called staticlib, which is a static library (.a file) that includes
the Rust runtime. That staticlib is then linked into libxul. For
supporting multiple crates, this approach breaks down, as linking
multiple copies of the Rust runtime is going to fail.

For supporting multiple crates, the approach taken here is to compile
each crate into a so-called rlib, which is essentially a staticlib
without the Rust runtime linked in. The build system takes note of
every crate destined for linking with libxul (treating them like static
libraries generated from C/C++ files), and generates a super-crate,
whimsically named "rul", that is compiled as a staticlib (so as to
include the Rust runtime) and then linked into libxul. Thus only one
copy of the Rust runtime is included, and the Rust compiler can take
care of any inter-crate dependencies.

This patch currently only supports Rust code in shared libraries, not in
binaries.
2016-04-21 09:54:01 -04:00
J.C. Jones 63f7ce5155 Bug 1244960 - Complete FIDO u2f NSSToken (Part 1). r=keeler, r=baku
- Merge in test changes from Bug 1255784.
- Remove the unnecessary mutex
- Stop doing direct memory work in NSS Token
- Clean up direct memory work in ContentParent
- In order to store persistent crypto parameters, the NSSToken had to move
  onto the main thread and be interfaced with via IDL/IPDL.
- Support Register/Sign via NSS using a long-lived secret key
- Rename the softtoken/usbtoken "enable" prefs, because of hierarchy issues
  with the WebIDL Pref shadowing.
- Also orders the includes on nsNSSModule.cpp
- Attestation Certificates are in Part 2.

Updates per keeler review comments:

- Use //-style comments everywhere
- Refactor the PrivateKeyFromKeyHandle method
- Rename the logging and fix extraneous NS_WARN_IF/logging combinations
- Other updates from review

April 11-12:

- Correct usage of the "usageCount" flag for PK11_UnwrapPrivKey
- Rebase up to latest

April 15:
- Rebase to latest

MozReview-Commit-ID: 6T8jNmwFvHJ

--HG--
extra : transplant_source : w%26%CES%2Cu%04%3EAl%04%2Cb%E2v%C9%08%3A%CC%F4
2016-04-15 09:29:12 -07:00
Chris Manchester 6a21a3345a Bug 1256979 - Move MOZ_CHROME_FILE_FORMAT to Python configure. r=glandium
The config variable is re-named to avoid confusion, because it is not set by
--enable-chrome-format.

MozReview-Commit-ID: 37gvjGGSkRc
2016-04-14 12:26:38 -07:00
Kai Engert 70551ded71 Bug 1258375, NSS_3_24_BETA6 and required adjustments to PSM and packaging, r=martin.thomson, r=glandium 2016-04-12 14:40:44 +02:00
Sebastian Hengst 364386e3cf Backed out changeset cb4b18566f30 and 7c4d19e3376f (bug 1163224) for build bustage. r=backout on a CLOSED TREE 2016-04-11 19:43:04 +02:00
Nathan Froyd e136c9ac20 Bug 1163224 - fix typo in creating global crate dependencies; r=me
Hoping the added Rust will let us reopen this CLOSED TREE.
2016-04-11 12:42:36 -04:00
Nathan Froyd 45af5cd66c Bug 1163224 - add build system support for multiple Rust crates; r=glandium
Our current build system support for Rust compiles any Rust crate into a
so-called staticlib, which is a static library (.a file) that includes
the Rust runtime.  That staticlib is then linked into libxul.  For
supporting multiple crates, this approach breaks down, as linking
multiple copies of the Rust runtime is going to fail.

For supporting multiple crates, the approach taken here is to compile
each crate into a so-called rlib, which is essentially a staticlib
without the Rust runtime linked in.  The build system takes note of
every crate destined for linking with libxul (treating them like static
libraries generated from C/C++ files), and generates a super-crate,
whimsically named "rul", that is compiled as a staticlib (so as to
include the Rust runtime) and then linked into libxul.  Thus only one
copy of the Rust runtime is included, and the Rust compiler can take
care of any inter-crate dependencies.

This patch currently only supports Rust code in shared libraries, not in
binaries.  The handling for the rul crate is placed in the common
backend, with a special hook for derived backends to handle shared
library objects.
2016-04-11 11:05:44 -05:00
Kai Engert f8da0365fd Backout revision 36f75c2863a1, bug 1258375 2016-04-11 17:00:39 +02:00
Kai Engert b471460db8 Bug 1258375, NSS_3_24_BETA5 and required adjustments to PSM and packaging, r=martin.thomson, r=glandium 2016-04-11 16:40:36 +02:00
Thomas Zimmermann 119b6d864d Bug 1262385: Fix %progbits for GAS' .section directive in ICU, r=ted
In contrast to the GNU AS manual, the syntax for the .section directive
uses '%progbits' instead of '@progbits'; at least on ARM. Looking at the
ICU tools and the generated files confirms this.
2016-04-07 09:45:22 +02:00
Wes Kocher 06944947a0 Backed out changeset 069c82269f81 (bug 1258375) for Windows xperf failures
MozReview-Commit-ID: DwhDorbB2PO
2016-04-06 16:51:48 -07:00
Gregory Szorc 8bec49cc68 Bug 1262569 - Do not print individual source targets being built; r=ted
Multiple people have complained that the build output of printing the
source files being built adds little value. I agree. The extra output
doesn't give really helpful progress info because sources can be built
in non-deterministic order. Furthermore, the extra output hides useful
output like compiler warnings.

This patch makes the default build system output even less verbose. We
no longer print the individual source targets when they are built. We do
still print the targets for binaries, so some sense of progress can be
inferred.

If people like verbosity, they can export the undocumented
BUILD_VERBOSE_LOG environment variable can be set to restore the old
behavior.

MozReview-Commit-ID: KeaeJJkjPJn

--HG--
extra : rebase_source : a90b4b82eeef48d9bd896b5c12907ce05a650d4d
2016-04-06 16:49:55 -04:00
Kai Engert 02dd23b86a Bug 1258375, NSS_3_24_BETA4 and required adjustments to PSM and packaging, r=martin.thomson, r=glandium 2016-04-06 21:43:36 +02:00
Tooru Fujisawa 3aedc7a677 Bug 933257 - Part 5: Use fdlibm in jsmath.cpp. r=jwalden 2016-01-07 12:30:29 +09:00
Tooru Fujisawa 8eb6e36c52 Bug 933257 - Part 3: Add build scripts for fdlibm. r=jwalden 2015-11-18 19:13:22 +09:00
Ted Mielczarek 58e2e722d0 bug 1239083 - use moz.build files to build ICU. r=glandium,waldo
Also fixes bug 926980 - load ICU data from an archive file.

Stop invoking ICU's autoconf build system. Instead, have hand-authored
moz.build files under config/external/icu to build what we need. In addition,
we'll commit a pre-built copy of the ICU data file (currently icudt56l.dat)
under config/external/icu/data to avoid having to build ICU host tools to
generate it. config/external/icu/data also contains some assembly files
which can generate an object file containing the ICU data file contents
so that the JS shell (or standalone JS builds) can be linked directly to
the data without having to deal with the external data file. This requires
yasm or GNU as.

Various bits of packaging have been updated to account for the ICU data file.
XPCOM initialization now sets the ICU data directory so ICU can locate its
data file.

The update-icu.sh script has been modified to read the list of C/C++ source
files out of the ICU Makefiles and update `sources.mozbuild` files under
config/external/icu, as well as build a local copy of ICU using its
autoconf build system to generate the ICU data file to be committed in-tree.


MozReview-Commit-ID: 8Pfkzqt6S1W

--HG--
extra : rebase_source : 31426cddddb5543e0191059ba2f2eb069abe7727
2016-04-05 10:09:12 -04:00
Ted Mielczarek 94fa8fd73a bug 1247396 - drop support for MOZ_SHARED_ICU. r=glandium
MozReview-Commit-ID: 54AQdzJqvvA

--HG--
extra : rebase_source : 41c2516bf65ca4594a68084a61d9a737680cfc9f
extra : source : e40580ed0fe6fab50f1d8d23747c2cf423d93016
2016-02-11 08:21:16 -05:00
Mike Hommey 2a512468b1 Bug 1260998 - Add support for HOST_CPPFLAGS for consistency. r=nalexander 2016-04-01 09:43:26 +09:00
Nick Alexander f2c9cdeaf9 Bug 1258760 - Allow re-signing already signed APK files. r=gps
Gradle produces signed, unaligned APK files.  We expect unsigned,
unaligned APK files.  This change discards any existing signature,
turning a signed, unaligned APK into an unsigned, unaligned APK.

Sadly |zip -q| does not silence a warning message about "nothing to
do" so we pipe to /dev/null.

MozReview-Commit-ID: DnSGJCvHsym

--HG--
extra : rebase_source : ee7884847767c0a075e3cfd404ba695d07f47e93
extra : histedit_source : 6aaa07eac03d69668f8556b84d1c1bae51c8ea22
2016-03-15 16:01:44 -07:00
Ted Mielczarek 509c7d11f9 bug 1257689 - move YASM check to moz.configure. r=mshal
MozReview-Commit-ID: KU3eSCsykPl

--HG--
extra : rebase_source : 4ec8256a4c772b61497ad442620aacb39f3b9ade
extra : amend_source : 258380912dcbcdb4dee2ac6737d71aa5328d12a7
extra : histedit_source : 9cabff8c5ba88ce541ea9881d9147dc4fb3a5692%2Cb1a74d8d449ebbbf5727a9665542043a5b122af7
2016-03-17 19:15:01 -04:00
Karl Tomlinson bc64779561 bug 1211892 read -unico-border-gradient of early Unico versions for ThreeDHighlight and ThreeDShadow r=acomminos
MozReview-Commit-ID: KWfQqT5MIjT

--HG--
extra : rebase_source : d480fe8538530aafd0b68da9b947f215af119bd1
2016-03-18 22:49:46 +13:00