CLOBBER
author Nathan Froyd <froydnj@mozilla.com>
Thu, 28 Jun 2018 09:04:41 -0400
changeset 479410 58e5f6f08c54a318e59cd5ef1482602e3a68ddf0
parent 478566 b2919970d120b33932ab3a28eb63bac865c3956e
child 480703 4a310672bb05b550e2b54da2c7dfc459aff488b0
permissions -rw-r--r--
Bug 1451104 - part 1 - ensure compatible binutils for GCC; r=glandium GCC will pick up whatever `as` is first in PATH when trying to assemble files. It expects this `as` to have at least as many features as the `as` detected at configure time when GCC was originally built. We should ensure that GCC is always picking up an appropriate `as` by adding its base directory to the search path; otherwise, we get peculiar assembler errors.

# 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.

Merge day clobber