CLOBBER
author Mike Hommey <mh+mozilla@glandium.org>
Tue, 02 Feb 2016 16:44:04 +0900
changeset 282756 d3d9deb0a4b1625c9194baf1c4435b88c75c33d4
parent 282192 a24f3a35d1c88c199af1693d82d9dafc70b3c4a2
child 283658 159e0a5a653f2789e0c9b94f41501a4a44f7cb34
permissions -rw-r--r--
Bug 1245013 - Move CMFLAGS/CMMFLAGS from config.mk to configure. r=mshal We don't really care to set those in js/src/configure because the JS engine doesn't use ObjC. We also don't care to preserve the += behavior because there were no AC_SUBST in the first place, so it's unlikely anyone has an override in their mozconfig and expects it to work.

# 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 1237983 - Investigate and remove the Bagheera Client implementation.