Currently, if the user specifies the environment variable 'CLANG', tests will attempt to use the value as a path to the clang executable. This patch expands this to work for lldb, clang++ and clang-cl, using the environment variables LLDB, CLANGPP, and CLANGCL. Note that previously, lldb could be specified via the CLANG environment variable, but this was almost certainly a bug, because that meant both clang and lldb would have the same path.

Currently, if the user specifies the environment variable 'CLANG', tests will attempt to use the value as a path to the clang executable. Previously, lldb could also be specified via the CLANG environment variable, but this was almost certainly a bug, because that meant both clang and lldb would have the same path. This patch changes the environment variable for lldb to 'LLDB'.

Currently, if the user specifies the environment variable 'CLANG', tests will attempt to use the value as a path to the clang executable. This patch expands this to work for lldb, clang++ and clang-cl, using the environment variables LLDB, CLANGPPPreviously, and CLANGCL. Note that previouslylldb could also be specified via the CLANG environment variable, lldb could be specified via the CLANG environment variablebut this was almost certainly a bug, but this was almost certainly a bug,because that meant both clang and lldb would have the same path. because that meant both clang and lldb would have the same pathThis patch changes the environment variable for lldb to 'LLDB'.