New Issue: Configure documentation inconsistent with behavior for '--prefix'?

Notifications Issues
1

26107, "lydia-duncan", "Configure documentation inconsistent with behavior for '--prefix'?", "2024-10-17T21:23:55Z"

I've been trying to use configure when setting up distribution of a Chapel library compiled into a Python package. In the documentation for configure, it says:

--prefix=/dir/for/install/ causes the Chapel compiler, libraries, and supporting code to be installed into the directories:

`/dir/for/install/bin`

`/dir/for/install/lib`

`/dir/for/install/share`

This technique is designed to install Chapel using a standard directory structure for the purposes of integrating it into a standard location that is already in your path, such as /usr/local/ or ~/.

To me, this indicated that ~/ was a valid value to use. But if I use ./configure --prefix=~/, then I get the following message:

error: expected an absolute directory name for --prefix: ~/

Was that an incorrect expectation to have? Is this a bug? Or is this a sign we should adjust our documentation to not imply that?