aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBill Wendling <isanbard@gmail.com>2011-10-19 09:47:00 +0000
committerBill Wendling <isanbard@gmail.com>2011-10-19 09:47:00 +0000
commit250c6801e4e16e4118fc130dff94dc89ea9332f1 (patch)
treebba2a55201c14f4e985ec0aff3eb4c856542a613
parentca58c722674ed7b564f68d1d9697cd01504edef2 (diff)
downloadexternal_llvm-250c6801e4e16e4118fc130dff94dc89ea9332f1.zip
external_llvm-250c6801e4e16e4118fc130dff94dc89ea9332f1.tar.gz
external_llvm-250c6801e4e16e4118fc130dff94dc89ea9332f1.tar.bz2
Duncan pointed out that sometimes CC and CXX are used to specify the compiler. Also that the configure script takes care of finding an appropriate compiler if one's not specified.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@142489 91177308-0d34-0410-b5e6-96231b3b80d8
-rwxr-xr-xutils/release/test-release.sh22
1 files changed, 2 insertions, 20 deletions
diff --git a/utils/release/test-release.sh b/utils/release/test-release.sh
index 00a1ac1..4255324 100755
--- a/utils/release/test-release.sh
+++ b/utils/release/test-release.sh
@@ -141,26 +141,8 @@ LogDir=$BuildDir/logs
mkdir -p $LogDir
# Find a compilers.
-c_compiler="`which clang`"
-if [ -z "$c_compiler" ]; then
- c_compiler="`which gcc`"
- if [ -z "$c_compiler" ]; then
- c_compiler="`which cc`"
- if [ -z "$c_compiler" ]; then
- echo "error: cannot find a working C compiler"
- fi
- fi
-fi
-cxx_compiler="`which clang++`"
-if [ -z "$cxx_compiler" ]; then
- cxx_compiler="`which g++`"
- if [ -z "$cxx_compiler" ]; then
- cxx_compiler="`which c++`"
- if [ -z "$cxx_compiler" ]; then
- echo "error: cannot find a working C++ compiler"
- fi
- fi
-fi
+c_compiler="$CC"
+cxx_compiler="$CXX"
# Make sure that the URLs are valid.
function check_valid_urls() {