# Missing Mason executable with Spack installation?

**URL:** <https://chapel.discourse.group/t/missing-mason-executable-with-spack-installation/45902>\
**Category:** Users\
**Created:** [November 5, 2025, 1:07pm UTC](https://chapel.discourse.group/t/missing-mason-executable-with-spack-installation/45902 "2025-11-05T13:07:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmag722](https://avatars.discourse-cdn.com/v4/letter/j/bbce88/32.png) [@jmag722](https://chapel.discourse.group/u/jmag722)\
**Post date:** [November 5, 2025, 1:07pm UTC](https://chapel.discourse.group/t/missing-mason-executable-with-spack-installation/45902/1 "2025-11-05T13:07:31Z")

</div>

Hello! Not sure if this is the right place for this, but I’ve installed Chapel via Spack, but do not have access to mason executable in my bin directory. Is there a certain configure option that needs to be selected for this?

`cd $CHPL_HOME` takes me to `~/opt/spack/opt/spack/linux-skylake/chapel-2.6.0-<hash>/share/chapel/2.6` but I don’t see a Makefile there to run `make mason` .

---

<div class="post-metadata">

**Author:** ![jabraham](https://yyz2.discourse-cdn.com/free1/user_avatar/chapel.discourse.group/jabraham/32/430_2.png) [@jabraham](https://chapel.discourse.group/u/jabraham)\
**Post date:** [November 5, 2025, 4:08pm UTC](https://chapel.discourse.group/t/missing-mason-executable-with-spack-installation/45902/2 "2025-11-05T16:08:51Z")

</div>

Unfortunately, I don't think mason is included in our spack package. The only tool included is chpldoc.

I'd encourage you to open a feature request for that on either [GitHub - spack/spack-packages: Spack's community package recipes](https://github.com/spack/spack-packages) or [GitHub - chapel-lang/chapel: a Productive Parallel Programming Language](https://github.com/chapel-lang/chapel).

-Jade

---

<div class="post-metadata">

**Author:** ![jmag722](https://avatars.discourse-cdn.com/v4/letter/j/bbce88/32.png) [@jmag722](https://chapel.discourse.group/u/jmag722)\
**Post date:** [November 6, 2025, 12:50pm UTC](https://chapel.discourse.group/t/missing-mason-executable-with-spack-installation/45902/3 "2025-11-06T12:50:26Z")

</div>

Link to issue:

> <https://github.com/chapel-lang/chapel/issues/28019>
>
> \### Summary of Feature
> 
> \*\*Description:\*\*
> Adding an option to build Mason when in…stalling Chapel via Spack.
> 
> \*\*Is this issue currently blocking your progress?\*\*
> No, I can use Cmake in the meantime, which I was planning on supporting anyways. I'd like to use Spack for all my dependencies (I used Spack to build LLVM for Chapel), but without Mason I'd need to make an exception there. Or have 2 versions of chapel installed (1 from Spack, other from Github).
> 
> \### Code Sample
> 
> \`\`\`chapel
> spack install chapel +mason
> mason ...
> \`\`\`