CLOBBER
author Tom Tromey <tom@tromey.com>
Thu, 04 May 2017 12:10:19 -0600
changeset 357147 8ce8c07e3e2928ef9d27c53225a6bb6a121799ba
parent 356854 bcca0465773f8a75863f35f75d6f2594df505c06
child 357355 0b1371055c7f890ed8cc265726747a35c67ead8f
permissions -rw-r--r--
Bug 1334279 - mark vsprintf-likes with MOZ_FORMAT_PRINTF; r=froydnj This annotates vsprintf-like functions with MOZ_FORMAT_PRINTF. This may provide some minimal checking of such calls (the GCC docs say that it checks for the string for "consistency"); but in any case shouldn't hurt. MozReview-Commit-ID: HgnAK1LiorE

# 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 1356927 - Mac builds in automation require a clobber for a change in which ranlib they use