From 59bd97bb893fd12e99d446aaa8abceb73c5b7afa Mon Sep 17 00:00:00 2001 From: Jack Nagel Date: Thu, 16 Feb 2012 16:55:28 -0600 Subject: Unset CLICOLOR_FORCE in the build environment If we're going to unset GREP_OPTIONS we may as well unset this one too, as it causes similar issues. Recent autoconf unset both of these. Fixes Homebrew/homebrew#8165. Signed-off-by: Jack Nagel --- Library/Homebrew/cmd/doctor.rb | 11 ----------- 1 file changed, 11 deletions(-) (limited to 'Library/Homebrew/cmd') diff --git a/Library/Homebrew/cmd/doctor.rb b/Library/Homebrew/cmd/doctor.rb index 5465a442f..b81a2f1a9 100644 --- a/Library/Homebrew/cmd/doctor.rb +++ b/Library/Homebrew/cmd/doctor.rb @@ -687,16 +687,6 @@ def check_for_MACOSX_DEPLOYMENT_TARGET end end -def check_for_CLICOLOR_FORCE - if ENV['CLICOLOR_FORCE'] - puts <<-EOS.undent - Having CLICOLOR_FORCE set can cause some builds to fail. - You may want to unset it. - - EOS - end -end - def check_for_other_frameworks # Other frameworks that are known to cause problems when present ["/Library/Frameworks/expat.framework", "/Library/Frameworks/libexpat.framework"].each do |f| @@ -851,7 +841,6 @@ module Homebrew extend self check_for_config_scripts check_for_dyld_vars check_for_MACOSX_DEPLOYMENT_TARGET - check_for_CLICOLOR_FORCE check_for_symlinked_cellar check_for_multiple_volumes check_for_git -- cgit v1.2.3