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
> stack path --compiler ghcjs-0.2.0_ghc-7.10.3 --local-install-root
Invalid argument `ghcjs-0.2.0_ghc-7.10.3'Auxiliary command not found in path `stack-path'File does not exist or is not a regular file `path'
Looks like in 2f7755d--compiler has been added to stack 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 in stack 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:
@mgsloan Well, for me it doesn't look like regression of #519. It's simply because newly added stack path-specific --compiler option clashes with general --compiler option, isn't it?
Anyway, as you suggested, specifying --compiler before path works. I was certain I checked that variant too, and it wasn't working, but now it works. Probably I messed up something while looking at this. Thanks! At least there's a way to fix my scripts.
I've pushed a commit to master that renames stack path --compiler to stack path --compiler-exe. I don't like how windows-ey the name is. If someone can think up something better, there's still time to change it!
I think this might be a good thing for a bugfix release - #2127