-
Notifications
You must be signed in to change notification settings - Fork 841
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
stack
not automatically installing alex
(build-tools
vs build-depends
?)
#782
Comments
What does your stack.yaml file look like? I think this feature won't work On Thu, Aug 13, 2015, 10:05 PM Eric Easley [email protected] wrote:
|
|
Right, that falls into the "custom build type" so it's not being covered. The workaround for now is to just run For the record, I don't have any intention of adding support for build-tool tracking for non-snapshot resolvers, since I can't think of a way to add it that won't absolutely kill performance. If someone else wants to take a crack at it, please speak up. |
Ah, so I ended up just adding |
Well, no matter what, you'll need to add the packages to the list of available packages in order to get it installed. The "special casing" is slightly more complicated than that, but for now the parsing of available executables only applies at the pre-process phase of a snapshot. It looks like the issue is resolved for now, so closing. |
This is not currently working for me; stack still can't find happy after running the build command with a ghc-7.10.3 resolver. I'm running: $ stack --version
Version 1.1.2 x86_64 hpack-0.14.1
$ cabal --version
cabal-install version 1.24.0.0
compiled using version 1.24.0.0 of the Cabal library with happy-1.19.5 in ~/.cabal/bin, ~/.local/bin, and after running the stack build command, under .stack-work as well. I think alex is working, so I'm not sure why they are treated differently. I'm seeing the following failure when running ...
setup-Simple-Cabal-1.22.5.0-ghc-7.10.3: The program 'happy' is required but it
could not be found |
@creswick: Are If so, can you share a sample project that we can use to reproduce the issue? |
Yeah, the resolver If I try to install a specific happy version, it nearly works:
|
@sjakobi Yes, both those directories are on my PATH; I don't have a minimal test case -- I'm sorry about that. |
Hello, maybe I'm missing something because I've just started to use
The problem is that when I run
Based on this I've also tried to put Any clue? 😄 Thanks. EDIT: Further info.
|
@GabVenturato your package seems to depend on
into your |
@qrilka Yes, that solved the problem! Thanks 😄 |
I may have strange behavioral expectations, but based on:
I'm expecting
stack build
to getalex
if necessary.Instead, for my project I get
Perhaps because
alex
is specified inbuild-tools
rather than build depends? https://github.com/erikd/language-javascript/blob/master/language-javascript.cabal#L41This is with
Version 0.1.3.1, Git revision 908b04205e6f436d4a5f420b1c6c646ed2b804d7
.The text was updated successfully, but these errors were encountered: