Paul Cadman 40e6648ae1 Use theJUVIX_LLVM_DIST_PATH environment variable to search for the clang executable (#2152) ... If set, `JUVIX_LLVM_DIST_PATH` should point to the root of a LLVM installation, i.e clang should be present in`$JUVIX_LLVM_DIST_PATH`/bin/clang. If `JUVIX_LLVM_DIST_PATH` is not set, or `clang` is not available there then the system PATH is used instead, (this is the current behaviour). The `juvix doctor` clang checks use the same logic as `juvix compile` to find and check the `clang` executable. To help with debugging the clang location, this PR also adds `juvix doctor --verbose` which prints the location of the `clang` executable and whether it was found using the system PATH or the JUVIX_LLVM_DIST_PATH environment variable: ``` juvix doctor --verbose > Checking for clang... | Found clang at "/Users/paul/.local/share/juvix/llvmbox/bin/clang" using JUVIX_LLVM_DIST_PATH environment variable ``` or ``` juvix doctor --verbose > Checking for clang... | Found clang at "/Users/paul/.local/bin/clang" using system PATH ``` * Closes https://github.com/anoma/juvix/issues/2133		2023-06-01 12:18:31 +02:00
..
Compile	Add main field to juvix.yaml (#2120)	2023-05-24 15:42:20 +02:00
Compile.hs	Use theJUVIX_LLVM_DIST_PATH environment variable to search for the clang executable (#2152)	2023-06-01 12:18:31 +02:00