Examples: http://mxr.mozilla.org/build/source/buildbot-configs/mozilla2/win32/mozilla-central/debug/mozconfig http://mxr.mozilla.org/build/source/buildbot-configs/seamonkey/win32/comm-central-trunk/debug/mozconfig { ac_add_options --enable-jemalloc ... ac_add_options --enable-trace-malloc } http://mxr.mozilla.org/build/source/buildbot-configs/thunderbird/win32/comm-central/debug/mozconfig { # Jemalloc gets disabled if trace-malloc is on, so don't bother enabling it here #ac_add_options --enable-jemalloc ac_add_options --enable-trace-malloc } Indeed: http://mxr.mozilla.org/mozilla-central/source/configure.in { 7227 if test "$NS_TRACE_MALLOC"; then 7228 MOZ_MEMORY= 7229 fi } This is not breaking anything, but it is rather useless and misleading! *** In addition, we should had an AC_MSG_WARN() in this case, to let the user know.

The mozconfigs are in the source tree now and someone already fixed it: cd mozilla-central/ grep jemalloc {b2g,browser}/config/mozconfigs/*/debug grep jemalloc mobile/*/config/mozconfigs/*/debug

(In reply to Nick Thomas [:nthomas] from comment #1) > The mozconfigs are in the source tree now Then shouldn't the moved /buildbot-configs/ files be removed too?