author Gregory Szorc <>
Mon, 14 Mar 2016 14:11:40 -0700
changeset 328503 7b559b11d4d1a07ba987fe5a2ec7b036a73185ef
parent 327766 ac43f8ec3958d0ba23310aee47d905dd40c1bf6a
child 328623 e2974ac0c94f60d020a7679c18f17a9b918b4ce1
permissions -rw-r--r--
Bug 1242005 - Disable C4359 to allow compilation on VS2015; r=kip The proper fix is to fix the underlying problem. However, I haven't touched C++ in months and I'm lazy. So I'm going for the quick fix so Visual Studio 2015 rollout is unblocked. MozReview-Commit-ID: 14cZCGPkx0V

# To trigger a clobber replace ALL of the textual description below,
# giving a bug number and a one line description of why a clobber is
# required. Modifying this file will make configure check that a
# clobber has been performed before the build can continue.
# MERGE NOTE: When merging two branches that require a CLOBBER, you should
#             merge both CLOBBER descriptions, to ensure that users on
#             both branches correctly see the clobber warning.
#                  O   <-- Users coming from both parents need to Clobber
#               /     \
#          O               O
#          |               |
#          O <-- Clobber   O  <-- Clobber
# Note: The description below will be part of the error message shown to users.
# Modifying this file will now automatically clobber the buildbot machines \o/

# Are you updating CLOBBER because you think it's needed for your WebIDL
# changes to stick? As of bug 928195, this shouldn't be necessary! Please
# don't change CLOBBER for WebIDL changes any more.

Bug 1253431 - Testing to see if a clobber fixes OSX debug build issues