External Issue: mason installation, binary maybe misplaced

19910, "lucaferranti", "mason installation, binary maybe misplaced", "2022-05-31T19:41:38Z"

Summary of Problem

When I installed chapel, the binary of chpl was placed in /usr/local/bin (as expected). When I installed mason, the binary was placed in chapel-1.26.0/bin/linux64-x86_64.

What confused me is that the docs says here

This installs mason in the same place as the chapel compiler (chpl) so that mason can be used anywhere in the user’s file system.

which was not the case in my situation.

I am no make wizard, but maybe the Makefile for mason (and other tools) could check if a configured-prefix has been generated and copy the binary to that path? Alternatively just adding a note in the docs would help too (happy to open a PR myself if it helps).

Steps to Reproduce

I installed chapel compiler with

cd chapel-1.26.0
./configure
make
make install

this placed the binary of the compiler into usr/local/bin.

I installed mason with

cd chapel-1.26.0
make mason

in case it's relevant I did not close the terminal session between chapel and mason installation. This placed the binary for mason under chapel-1.26.0/bin/linux64-x86_64.

Configuration Information

  • Output of chpl --version:
chpl version 1.26.0
  built with LLVM version 12.0.0
Copyright 2020-2022 Hewlett Packard Enterprise Development LP
Copyright 2004-2019 Cray Inc.
(See LICENSE file for more details)
  • Output of $CHPL_HOME/util/printchplenv --anonymize:
CHPL_TARGET_PLATFORM: linux64
CHPL_TARGET_COMPILER: llvm
CHPL_TARGET_ARCH: x86_64
CHPL_TARGET_CPU: native
CHPL_LOCALE_MODEL: flat
CHPL_COMM: none
CHPL_TASKS: qthreads
CHPL_LAUNCHER: none
CHPL_TIMERS: generic
CHPL_UNWIND: none
CHPL_MEM: jemalloc
CHPL_ATOMICS: cstdlib
CHPL_GMP: bundled
CHPL_HWLOC: bundled
CHPL_RE2: bundled
CHPL_LLVM: system
CHPL_AUX_FILESYS: none
  • Back-end compiler and version, e.g. gcc --version or clang --version:
gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
  • (For Cray systems only) Output of module list: