Hi - I'd recommend you adjust your PATH to include the clang you are trying to use and then use CHPL_HOST_COMPILER=clang. You'll know you've done so correctly when `which clang` indicates the version you are trying to use.
In some cases, you might be able to work with the clang source tree bundled with Chapel. You'd do that by setting CHPL_HOST_COMPILER=clang-included. Chapel releases use LLVM/Clang 3.6, although I have a branch which has support for 3.7. Regarding Kalmar, I'm not familiar with this project but I believe you'd only need to build the Chapel runtime with Kalmar and then use Kalmar as the backend C compiler for Chapel. (In other words, you'd just want to adjust the target compiler configuration ... but that won't work until somebody adds the Makefile support for that compiler). >From the Kalmar web pages, it looks like it works with a clang installation. Can you figure out how to extend make/compiler/Makefile.clang to support Kalmar? Cheers, -michael On 9/8/15, 1:03 AM, "Bibek Ghimire" <[email protected]> wrote: >Hello, > I was trying to build chapel compiler using clang. I know I >could do like: > CHPL_HOST_COMPILER=clang, but the thing is I want to also specify >specific path (where ever clang resides). > > >Also another follow up question .. I was trying to use kalmar to build >chapel compiler, has anyone tried this .. if not can anyone help me how I >should start. My initial guess was some how supply the compiler path and >then resolve the error during the > building of chapel compiler. > > >-Bibek > ------------------------------------------------------------------------------ _______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
