From 347b7bb51d607d1de7fcce00be5daf532c7e56dc Mon Sep 17 00:00:00 2001 From: Per Lundberg Date: Wed, 25 May 2016 00:26:31 +0300 Subject: [PATCH] Redirect stderr to /dev/null We already redirect stdout, but the problem is that (at least on Windows/MSYS2), the `which` command tends to output things to stderr when failing: ``` $ ./mach build -d which: no python2.7 in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/c/Program Files/Java/jdk1.8.0_66/bin:/c/Python27:/c/Python27/Scripts) ``` This PR silences this noise. --- mach | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mach b/mach index 9d42641fa2a..4fb1f0d62eb 100755 --- a/mach +++ b/mach @@ -6,7 +6,7 @@ # The beginning of this script is both valid shell and valid python, # such that the script starts with the shell and is reexecuted with # the right python. -'''which' python2.7 > /dev/null && exec python2.7 "$0" "$@" || exec python "$0" "$@" +'''which' python2.7 > /dev/null 2> /dev/null && exec python2.7 "$0" "$@" || exec python "$0" "$@" ''' from __future__ import print_function, unicode_literals