-
Notifications
You must be signed in to change notification settings - Fork 701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"In-place"d build-tools not made available via $PATH #5104
Comments
+1. |
any news on this? i think i'm being bitten by this while building https://github.com/ghcjs/domconv-webkit |
fgaz
added a commit
to fgaz/cabal
that referenced
this issue
Oct 21, 2018
Monolithic inplace packages have a directory for each exe, so we allow multiple paths and return all the exe paths of the package. Fixes haskell#5104
fgaz
added a commit
to fgaz/cabal
that referenced
this issue
Oct 21, 2018
Monolithic inplace packages have a directory for each exe, so we allow multiple paths and return all the exe paths of the package. Fixes haskell#5104
fgaz
added a commit
to fgaz/cabal
that referenced
this issue
Oct 29, 2018
Monolithic inplace packages have a directory for each exe, so we allow multiple paths and return all the exe paths of the package. Fixes haskell#5104
fgaz
added a commit
to fgaz/cabal
that referenced
this issue
Oct 29, 2018
Monolithic inplace packages have a directory for each exe, so we allow multiple paths and return all the exe paths of the package. Fixes haskell#5104
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that
build-tools
which become in-place, don't end up being locatable via$PATH
.I noticed this when trying to
cabal new-build exe:cabal
in Git's cabal-2.0 branch:And if we look at plan.json, we can clearly see that
pretty-show
depends on the inplacehappy-1.19.8-inplace
build-tool:whose executable can be found in
dist-newstyle
:The text was updated successfully, but these errors were encountered: