Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Unified Diff: configure.in

Issue 29342994: Issue 2490 - Investigate another way to disable the crash reporter (Closed)
Patch Set: Force disable crashreporter without removing upstream code Created Oct. 25, 2016, 1:38 p.m.
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: configure.in
===================================================================
--- a/configure.in
+++ b/configure.in
@@ -6068,16 +6068,19 @@ MOZ_ARG_DISABLE_BOOL(crashreporter,
[MOZ_CRASHREPORTER=F # Force enable breakpad])
if test "$OS_ARCH" != "$HOST_OS_ARCH" -a "$OS_ARCH" != "WINNT" -a "$OS_ARCH" != "Darwin"; then
if test "$MOZ_CRASHREPORTER" = F; then
AC_MSG_ERROR([Cannot --enable-crashreporter, as breakpad tools do not support compiling on $HOST_OS_ARCH while targeting $OS_ARCH.])
fi
MOZ_CRASHREPORTER=
fi
+# Force disable crashreporter
Felix Dahlke 2016/10/25 15:15:03 Ultra nit: I guess I'd add an empty line on top of
diegocarloslima 2016/10/25 15:17:12 Ok, I'll add that
+# See https://issues.adblockplus.org/ticket/2490
+MOZ_CRASHREPORTER=
if test -n "$MOZ_CRASHREPORTER"; then
AC_DEFINE(MOZ_CRASHREPORTER)
if test "$OS_TARGET" = "Linux" -o "$OS_ARCH" = "SunOS" && \
test -z "$SKIP_LIBRARY_CHECKS"; then
PKG_CHECK_MODULES(MOZ_GTHREAD, gthread-2.0)
fi
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld