You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current build infrastructure at several points makes the assumption that stack will be in the path once it is installed during the build. This assumption is not generally true. In a sandboxed build like that by brew install -s the PATH is minimal and this causes the build to fail at several places. The earliest failure is the call to etc/build/install-stack.sh where in the second-last line of the script which stack returns an empty string, and the script then returns an error on the last line stack --version which terminates the build.
One solution is to replace in the Makefile each
@command
with
@env "PATH=${BIN_DIR}:${PATH}" command
I've tested this and it seems to work for brew install -s with a minimalist formula. This change would also remove the need to tell the user about setting PATH in the documentation.
Todo:
check the idiomatic way to implement this pattern (I suspect it is common)
check this change would not break builds on Windows and Linux
The text was updated successfully, but these errors were encountered:
The current build infrastructure at several points makes the assumption that
stack
will be in the path once it is installed during the build. This assumption is not generally true. In a sandboxed build like that bybrew install -s
thePATH
is minimal and this causes the build to fail at several places. The earliest failure is the call toetc/build/install-stack.sh
where in the second-last line of the scriptwhich stack
returns an empty string, and the script then returns an error on the last linestack --version
which terminates the build.One solution is to replace in the Makefile each
with
I've tested this and it seems to work for
brew install -s
with a minimalist formula. This change would also remove the need to tell the user about settingPATH
in the documentation.Todo:
The text was updated successfully, but these errors were encountered: