Specifying compiler for `stack path` is not working anymore #2123
Comments
Argh! Seems like this is a regression of #519
|
@mgsloan Well, for me it doesn't look like regression of #519. It's simply because newly added |
Ah sorry, I had overlooked some comment's here. |
My mistake, we shouldn't have used |
I've pushed a commit to master that renames I think this might be a good thing for a bugfix release - #2127 |
I have a project I build with two compilers simultaneously (specifically, server and client part of which built by ghc and ghcjs respectively). With stack 1.0.4.3 I can do this:
> stack path --compiler ghcjs-0.2.0_ghc-7.10.3 --local-install-root /home/user/project/.stack-work/install/x86_64-linux/lts-5.14/ghcjs-0.2.0_ghc-7.10.2
Since stack 1.1.0 I get:
Looks like in 2f7755d
--compiler
has been added tostack path
as an option to print out path to compiler's binary, which overrides general meaning of--compiler
as an option specifying compiler to use.--compiler
still works in other commands as before, for example instack build
.Could the new
--compiler
option be renamed to something else? Is there a way now to get compiler-specific stack paths?The text was updated successfully, but these errors were encountered: